Afternoon all,
I'm buried in designing a build repository for our cluster, and am looking
for any pointers to tools that people have written to manage the portage tree,
especially with respect to predicting the effect of updates to the tree on the
packages in given chroot-able build trees for a central package repository.
I am planning on building all the packages for a given
architecture/configuration in a chroot tree that bind-mounts the portage tree
from a central copy maintained on the build server, and installs the packages
into a similarly mounted sub-directory of a /usr/portage/packages directory.
What I am hoping to accomplish is to be able to run a weekly emerge -Duvp
against the a current copy of the portage tree and generate a message that would
tell me what would be changed, without permanently updating the tree to a newer
version. Ideally, finding a mechanism for selectively updating the tree on a
package by package basis would be nice, but that's a future problem I think. I
suspect the best way to accomplish some of this would be to essential mirror the
portage tree in cvs or subversion locally, but I'd rather not start from
scratch. If anyone has set something like this and has any experience or
scripts that they can share to give me a running start, I would be most grateful
Thanks,
Andy
PS: at one point, there was a website about a university lab in New Zealand that
had a centralized package repository system running under Gentoo. I can't seem
to find this page anymore. Does anyone have a pointer to it? thanks. adf
--
Andrew Fant | The lion and the calf shall lie | Disclaimer:
[EMAIL PROTECTED] | down together, but the calf won't | Do you REALLY
TCCS/USG | get much sleep. | think I can
Tufts University | W. Allen | speak for Tufts?
--
[email protected] mailing list
