From: Nick Jones <carpaski@twobit.net>
To: Chris Frey <cdfrey@netdirect.ca>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] emerge regen
Date: Sun, 4 Jan 2004 03:20:03 -0600 [thread overview]
Message-ID: <20040104092003.GA32032@twobit.net> (raw)
In-Reply-To: <20031230224401.A22479@netdirect.ca>
> Can anyone point me at documentation describing what the 'regen'
> option does on emerge? The man page is the only place I've found,
> and it basically tells me to use rsync.
>
> What I want to do is create a separate portage tree that I can
> manually rync into, and copy over .ebuild files as I need them, into the
> main /usr/portage tree.
emerge regen causes portage to generate all missing cache entries
for any ebuild in the portage tree, as well as regenerate the ones
marked as expired due to an eclass change or the ebuild itself
changing.
It's a forced caching, basically. 'emerge sync' does the same thing
but does it with an extreme difference in speed by using the cache
that's generated on gentoo's servers. A complete regeneration can
take upwards of two hours, depending on the speed of the machine.
I'm not entirely certain what you're doing but the only use for
this function for non-cvs users is for the generation of a metadata
cache. As Gentoo does this itself, it seems unlikely that this
really is going to benefit anything you're trying to accomplish,
unless you have a _very_ large set of ebuilds that you're
incorporating into a private rsync tree.
--NJ
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2004-01-04 9:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-31 3:44 [gentoo-dev] emerge regen Chris Frey
2004-01-04 9:20 ` Nick Jones [this message]
2004-01-10 3:34 ` N. Owen Gunden
2004-01-10 4:59 ` Georgi Georgiev
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040104092003.GA32032@twobit.net \
--to=carpaski@twobit.net \
--cc=cdfrey@netdirect.ca \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox