| 1 |
On Fri, Apr 12, 2013 at 11:21:01AM -0400, Rick "Zero_Chaos" Farina wrote: |
| 2 |
> On 04/12/2013 11:12 AM, W. Trevor King wrote: |
| 3 |
> > This commit adds a warning in the pkgcache documentation that should |
| 4 |
> > help people understand what might be going wrong if they see similar |
| 5 |
> > linking errors. For more details, see the thread following |
| 6 |
> > http://thread.gmane.org/gmane.linux.gentoo.catalyst/2137/focus=2193 |
| 7 |
> |
| 8 |
> NACK. Personally I love this idea but I'm really against having a link |
| 9 |
> to a ML discussion, no one is going to quit configuring catalyst in the |
| 10 |
> middle to read a ML discussion... |
| 11 |
|
| 12 |
Well, that's the commit message, but… |
| 13 |
|
| 14 |
> > diff --git a/files/catalyst.conf b/files/catalyst.conf |
| 15 |
> > index b74c546..e285e4f 100644 |
| 16 |
> > --- a/files/catalyst.conf |
| 17 |
> > +++ b/files/catalyst.conf |
| 18 |
> > @@ -58,7 +58,11 @@ hash_function="crc32" |
| 19 |
> > # kerncache = keeps a tbz2 of your built kernel and modules (useful if your |
| 20 |
> > # build stops in livecd-stage2) |
| 21 |
> > # pkgcache = keeps a tbz2 of every built package (useful if your build stops |
| 22 |
> > -# prematurely) |
| 23 |
> > +# prematurely. However, you may see linking problems if the binary |
| 24 |
> > +# package was built against an older version of a runtime dependency |
| 25 |
> > +# and the package in question is not using EAPI5's sub-slots. For |
| 26 |
> > +# further discussion, see |
| 27 |
> > +# http://article.gmane.org/gmane.linux.gentoo.catalyst/2224) |
| 28 |
> > # seedcache = use the build output of a previous target if it exists to speed up |
| 29 |
> > # the copy |
| 30 |
> > # snapcache = cache the snapshot so that it can be bind-mounted into the chroot. |
| 31 |
|
| 32 |
Here I link to the ML from the config file ;). I'm fine linking |
| 33 |
somewhere else (doc/catalyst-conf.1.txt?). Then config file comments |
| 34 |
could move to the new man page (as spec file comments moved to their |
| 35 |
own man page). With more space, we can wax eloquent on the potential |
| 36 |
pkgcache issues ;). |
| 37 |
|
| 38 |
Cheers, |
| 39 |
Trevor |
| 40 |
|
| 41 |
-- |
| 42 |
This email may be signed or encrypted with GnuPG (http://www.gnupg.org). |
| 43 |
For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy |
Archives