| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
On 04/12/2013 11:33 AM, W. Trevor King wrote: |
| 5 |
> On Fri, Apr 12, 2013 at 11:21:01AM -0400, Rick "Zero_Chaos" Farina wrote: |
| 6 |
>> On 04/12/2013 11:12 AM, W. Trevor King wrote: |
| 7 |
>>> This commit adds a warning in the pkgcache documentation that should |
| 8 |
>>> help people understand what might be going wrong if they see similar |
| 9 |
>>> linking errors. For more details, see the thread following |
| 10 |
>>> http://thread.gmane.org/gmane.linux.gentoo.catalyst/2137/focus=2193 |
| 11 |
>> |
| 12 |
>> NACK. Personally I love this idea but I'm really against having a link |
| 13 |
>> to a ML discussion, no one is going to quit configuring catalyst in the |
| 14 |
>> middle to read a ML discussion... |
| 15 |
> |
| 16 |
> Well, that's the commit message, but… |
| 17 |
> |
| 18 |
Yeah sorry, a bit distracted, I meant to protest on the below section |
| 19 |
>>> diff --git a/files/catalyst.conf b/files/catalyst.conf |
| 20 |
>>> index b74c546..e285e4f 100644 |
| 21 |
>>> --- a/files/catalyst.conf |
| 22 |
>>> +++ b/files/catalyst.conf |
| 23 |
>>> @@ -58,7 +58,11 @@ hash_function="crc32" |
| 24 |
>>> # kerncache = keeps a tbz2 of your built kernel and modules (useful if your |
| 25 |
>>> # build stops in livecd-stage2) |
| 26 |
>>> # pkgcache = keeps a tbz2 of every built package (useful if your build stops |
| 27 |
>>> -# prematurely) |
| 28 |
>>> +# prematurely. However, you may see linking problems if the binary |
| 29 |
>>> +# package was built against an older version of a runtime dependency |
| 30 |
>>> +# and the package in question is not using EAPI5's sub-slots. For |
| 31 |
>>> +# further discussion, see |
| 32 |
>>> +# http://article.gmane.org/gmane.linux.gentoo.catalyst/2224) |
| 33 |
>>> # seedcache = use the build output of a previous target if it exists to speed up |
| 34 |
>>> # the copy |
| 35 |
>>> # snapcache = cache the snapshot so that it can be bind-mounted into the chroot. |
| 36 |
> |
| 37 |
> Here I link to the ML from the config file ;). I'm fine linking |
| 38 |
> somewhere else (doc/catalyst-conf.1.txt?). Then config file comments |
| 39 |
> could move to the new man page (as spec file comments moved to their |
| 40 |
> own man page). With more space, we can wax eloquent on the potential |
| 41 |
> pkgcache issues ;). |
| 42 |
|
| 43 |
Yeah, but more reading is not necessarily more better. It is likely |
| 44 |
better if we explain it briefly and not worry about 100% of the details. |
| 45 |
the config file isn't meant for long discussions, it's meant for short |
| 46 |
recommendations and warnings about features at most. |
| 47 |
|
| 48 |
- -ZC |
| 49 |
> |
| 50 |
> Cheers, |
| 51 |
> Trevor |
| 52 |
> |
| 53 |
|
| 54 |
-----BEGIN PGP SIGNATURE----- |
| 55 |
Version: GnuPG v2.0.19 (GNU/Linux) |
| 56 |
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ |
| 57 |
|
| 58 |
iQIcBAEBAgAGBQJRaDIXAAoJEKXdFCfdEflKLrYQAJcGiOnYWEQcRvFMiG+B+494 |
| 59 |
YmyaPyMIS0qaFgN8n5q6wh3AtEM/eXyleff7Bnqulktgb89iNFwCtaXlKsVDygOD |
| 60 |
dSRES11nccc+Y96Mve3OujAj0kp7XoVytGRCmsQJsofrtSOWjaebD4UyxQduaWJN |
| 61 |
Q01WpgfdTrTMXmfozHs+FrAm0Vo+C/t3mJr/TrPGxXdaHp0ee8tCuh7PAmGvw6hy |
| 62 |
lRkmrl6FpsXpytwsuL+ekIKMiCfZ5KIkdzLN3qVil2eZ6YRokxbD7WZsPElLQKud |
| 63 |
lTdei62NuIP1+cdTfzqxyv9hF+480OIF40fZh4L9XHlW1aS1BfHGiq6WgNis0nz6 |
| 64 |
cBZE0/JR+JJr6p2BWZ7imAIldB2vyCgvQuaKEPS59HhIHjwDqfLZtR6B/SmXWiPE |
| 65 |
gVLgFipuvNjmBe1swDpAUHpeLYh7DlksYVeoYJbG4V6WLT55Aa7Oa0gGWJUYIzfY |
| 66 |
WX9wiifb//b0J0O83C6dLWcL9yyDCPMlL+MW/kjQ4Js2f+aaSfVL62mFp/XFUC2g |
| 67 |
p5NrOD5AcJDvExQ0peOZjED+50S2AN/7tlmBJ2OpkKtIAxFzyanwvp167GcjGGXM |
| 68 |
wtONk58744rUlq4Na9I81ybxchjaxATwlxx2CIRcutFoqXx7C9boWaddUgYiB0qf |
| 69 |
OGmFQH/fuKhOgZI3k1P5 |
| 70 |
=bjco |
| 71 |
-----END PGP SIGNATURE----- |
Archives