On Fri, Apr 12, 2013 at 02:47:05PM -0400, Rick "Zero_Chaos" Farina wrote:
> On 04/12/2013 02:21 PM, W. Trevor King wrote:
> > +ccache::
> > +Enable build time ccache support.
> Warning, ccache has been known to cause random build failures and bugs
> reported with ccache enabled may be closed invalid.

Added for v3.

> > +kerncache::
> > +Keep a `tbz2` of your built kernel and modules.  This is useful if
> > +your build dies during `livecd-stage2`.
> kerncache keeps a full dir of everything like seedcache does.

For v3, I'll use:

  kerncache::
  Keep a copy of the built kernel and modules.  This is useful if your
  build dies during `livecd-stage2`.

> > +pkgcache::
> > +Keep a ``tbz2`` of every built package.  This is useful if your build
> > +dies prematurely.
> Might be easier to just say this enables the binpkg feature of portage...

Do you mean `emerge --usepkg --buildpkg`?  How about:

  pkgcache::
  Enable `--usepkg` and `--buildpkg` for most *emerge(1)* runs.  This is
  useful if your build dies prematurely.  However, you may experience
  linking problems.  See the *BINARY PACKAGE DEPENDENCIES* section for
  details.

> > +snapcache::
> > +Cache the snapshot so that it can be bind-mounted into the chroot.
> > +WARNING: moving parts of the portage tree from within fsscript *will*
> > +break your cache.  The cache is unlinked before any empty or rm
> > +processing, though.
> - -, though

Added to v3.

> > +*storedir*::
> > +Location for built seeds, temporary files, and caches.
> mention the default location

For v3:

  *storedir*::
  Location for built seeds, temporary files, and caches (example:
  `/var/tmp/catalyst`).

Thanks!
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