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