[gentoo-dev] emerge regen

[gentoo-dev] emerge regen

[Chris Frey]

Hi,

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.

It appears that I can use regen for this purpose after copying
new files in, but I want to make sure it is supposed to do what
I'm hoping it will. :-)

Thanks,
- Chris


--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] emerge regen

[Nick Jones]

> 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

Re: [gentoo-dev] emerge regen

[N. Owen Gunden]

On Sun, Jan 04, 2004 at 03:20:03AM -0600, Nick Jones wrote:
> 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.

Where are these cache entries stored?  If I mount /usr/portage over NFS,
do I get the new cache entries on an emerge sync?

 - O

--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] emerge regen

[Georgi Georgiev]

maillog: 09/01/2004-22:34:40(-0500): N. Owen Gunden types
> On Sun, Jan 04, 2004 at 03:20:03AM -0600, Nick Jones wrote:
> > 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.
> 
> Where are these cache entries stored?  If I mount /usr/portage over NFS,
> do I get the new cache entries on an emerge sync?

/var/cache/edb/dep

-- 
/\   Georgi Georgiev   /\ Half the world is composed of people who     /\
\/    chutz@gg3.net    \/ have something to say and can't, and the     \/
/\  +81(90)6266-1163   /\ other half who have nothing to say and keep  /\
\/ ------------------- \/ on saying it.                                \/

--
gentoo-dev@gentoo.org mailing list