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…

> > 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 ;).

Cheers,
Trevor

-- 
This email may be signed or encrypted with GnuPG (http://www.gnupg.org).
For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy