[gentoo-user] question re creating meta-ebuild for application distribution
A question about using Gentoo's meta-distribution aspect: I'm about to use a local meta-ebuild to deploy a set of applications across a group of servers. I'd rather not add this ebuild to an existing package directory -- I'd rather use app-$mycompanyname -- but when I do so, I see that portage doesn't know about the new package directory when I do an emerge -s $myappname. This isn't a big deal in and of itself, since the ebuild seems to merge and unmerge without problems, but is there a way I can locally add a new package directory so that portage fully knows about it? Can I do so in such a way that an emerge rsync won't lose that information? And if not, I am going to run into other problems by using an unsupported pkg location? Thanks, Jacob Smullyan pgp0.pgp Description: PGP signature
Re: [gentoo-user] question re creating meta-ebuild for application distribution
On Wed, 2003-10-15 at 11:20, Sigurd Stordal wrote: directory so that portage fully knows about it? Can I do so in such a way that an emerge rsync won't lose that information? And if not, I PORTDIR_OVERLAY. You set it in the make.conf file, and make every new app dir there, will not be updated by emerge sync. I am using PORTDIR_OVERLAY. But simply creating a new package directory within it doesn't solve the problem. To see this, try creating a new subdirectory $PORTDIR_OVERLAY/app-whatever, create an application directory within it, and a valid ebuild within it. Do an ebuild digest, then emerge app-whatever/whatever/whatever-1.0.ebuild. It should install fine. Then do an emerge -s whatever. It won't find your ebuild. So package directories must be registered somehow with portage, but I don't know the mechanism. js -- [EMAIL PROTECTED] mailing list
