Re: [gentoo-dev] Using cvs as your portage directory

[Chris Gianelloni]

On Tue, 2004-03-23 at 18:55, Brandon Hale wrote:
> On Tue, 2004-03-23 at 23:10 +0000, Stuart Herbert wrote:
>
> This may or may not be of use to any of you, but here is how I do
> things.. My main tree (/usr/portage) uses typical rsync, this is what I
> sync nightly. Note that a nightly rsync update is less stressful on our
> infrastructure as we have numerous mirrors for just this purpose. I have
> an overlay in /usr/local/portage for things that I'm playing with but
> have no intentions to commit. This is my PORTDIR_OVERLAY in make.conf.
> Lastly, I have a cvs checkout of the tree in ~/work/gentoo-x86 to
> develop against. If I want to test something in the tree, I can simply
> pass PORTDIR_OVERLAY inline and override the variable in the environment
> (this might be additive, doesnt matter either way), such as
> `PORTDIR_OVERLAY="~/work/gentoo-x86" emerge foo`. With some $1 action,
> this lends itself to a simple alias.
>
> What are the pros? I have a complete and up to date tree w/o putting
> unneeded stress on our infra. I also have a place for testing ebuilds I
> am not ready to commit. And most importantly to me, I can also work on
> the tree in CVS w/o any extra hassle. Any questions, or improvements on
> the above feel free to drop me a line.

This is exactly what I do, minus the updating of my /usr/portage
nightly.  I probably only update once a week or so on most of my
machines, unless I am working on something specific which requires it.

I like to keep my trees separate, and even go so far as to keep a VMWare
image of x86 to fire up and test things on when I'm making changes to
the stable tree for x86 rather than ~x86.

-- 
Chris Gianelloni
Developer, Gentoo Linux
Games Team

Is your power animal a penguin?