1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
On 04/19/2013 12:18 PM, W. Trevor King wrote: |
5 |
> On Fri, Apr 19, 2013 at 10:11:50AM -0400, Rick "Zero_Chaos" Farina wrote: |
6 |
>> On 04/16/2013 03:42 PM, W. Trevor King wrote: |
7 |
>>> From: "W. Trevor King" <wking@×××××××.us> |
8 |
>>> |
9 |
>>> The current approach to avoiding problems due to stale binary packages |
10 |
>>> with untracked ABI dependencies is to disable binpkg use during |
11 |
>>> troublesome sections of the build (e.g. seed updates). I think that a |
12 |
>>> cleaner solution would be to use a configurable spec option |
13 |
>>> blacklisting binpkgs for troublesome packages. For example, in a |
14 |
>>> stage1 with update_seed enabled, the Portage emerge (before the seed |
15 |
>>> update) has: |
16 |
>> |
17 |
>> This needs to remain optional. |
18 |
> |
19 |
> It is optional. Just set `binpkg_blacklist` explicitly to an empty |
20 |
> string if you don't want to blacklist the default packages (currently |
21 |
> only two). |
22 |
> |
23 |
>> I'm not going to nack a patch that some people may find useful but |
24 |
>> in my personal opinion this is a terrible solution that should not |
25 |
>> be used. We need to find a way to rebuild packages as needed (like |
26 |
>> EAPI 5) not force a rebuild everytime. |
27 |
> |
28 |
> Agreed, but in the absence of one of the following: |
29 |
> |
30 |
> * a tree full of EAPI-5+ packages that correctly use ABI sub-slotting |
31 |
> (if I live long enough to see this, I'll be very happy ;), |
32 |
> * local overlays fixing ABI sub-slotting (maintained by folks without |
33 |
> much experience in the packages in question?), or |
34 |
> * Portage tweaks to work around packages that don't use EAPI-5+ (or |
35 |
> that do, but don't use ABI sub-slots appropriately). |
36 |
> |
37 |
> I'm fairly confident that none of those are happening in the next six |
38 |
> months, and there seems to be agreement that catalyst needs some sort |
39 |
> of local hack to work around the problem until one of the real |
40 |
> solutions lands. |
41 |
> |
42 |
> The `binpkg_blacklist` option lets you name (on a per-package level) |
43 |
> troublesome packages that get ABI sub-slots wrong (or don't even try). |
44 |
> I think that this approach will force *fewer* rebuilds than the |
45 |
> current approach (from e7ea409 and 6c0a577) which blacklists |
46 |
> everything from the seed update. |
47 |
> |
48 |
> Another (non-exclusive) possibility is to put a big warning on the |
49 |
> binpkgs option [1] and leave it up to folks to use at their own risk. |
50 |
|
51 |
As I already stated, I have no issue allowing this into the code base as |
52 |
one option people can use. It may be a good idea to make this patch |
53 |
depend on your other patchset which fixes up some of the documentation |
54 |
and adding more detailed documentation....unless you already did that |
55 |
and I'm not paying attention. |
56 |
|
57 |
Thanks, |
58 |
Rick |
59 |
> |
60 |
> Cheers, |
61 |
> Trevor |
62 |
> |
63 |
> [1]: http://mid.gmane.org/cover.1366075786.git.wking@×××××××.us |
64 |
> |
65 |
|
66 |
-----BEGIN PGP SIGNATURE----- |
67 |
Version: GnuPG v2.0.19 (GNU/Linux) |
68 |
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ |
69 |
|
70 |
iQIcBAEBAgAGBQJRcXGOAAoJEKXdFCfdEflKy8sP/jjNADHnnzt2vl8suWHt3LlL |
71 |
pKuyKwjN9GDdhQJrzLZKYmQZNEFfT+GYUq+Z6zTpuR2fE7+d6SCJZDOOIpjO/cMh |
72 |
MUMxn+E49rwMo3IPX/ZuaXAAH0OINM2NFg5paX1jorN+WRXmKkvAJQbbRuBAWSBo |
73 |
OxKz7XsldEjELgCch5/yJH7as8mITFqcheXVMXLOS6xYKCbSHOpnP2s6+KMLlon5 |
74 |
Tw/DNviKvGOGQtLLd4ZWzqic0ElbQUmZIBNpWxODIbfmb2dH46/Xa2pybUOxqm+6 |
75 |
VVhrDxNbEaHNirNxTx3DrWyaeg6Dz/KSEoWHSOYy8DYgg+sIFWrC5RLHg21uWdhU |
76 |
rGtGnj61hjjuKNsQlzyhFRH7Mxn8fOcktVFfbW1l2Mnvqr0zJbuKeyupt/vpyVHH |
77 |
bTZL0PBNSPX9YrMQD3wrpW4UxUMBLQCfAfSmNRsb3vtXXjGnI2Q7bmLQnv86Vqau |
78 |
J6QED7g+AvzqmLXqUU2RpYs3/H5yv1aJNH4yGNrr6vUvQOnoA3nRH5OF2hB+G+p8 |
79 |
JNWSu88IuMqk2h/+KJVGmSEZlBhfsjoW+yUGLncrdQ1nI4ir3IZxjDvXCdLNG31f |
80 |
Ic8drzEfra9ls4MTCAvFFOY3MCEH16IBqNXodv56FNmA70qmHlXoamyOp5Lwiftv |
81 |
e6jQsxZ078bxvcQKGAcB |
82 |
=bjhe |
83 |
-----END PGP SIGNATURE----- |