Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 237917 - add support for package.keywords in profiles
Summary: add support for package.keywords in profiles
Status: RESOLVED DUPLICATE of bug 55321
Alias: None
Product: Portage Development
Classification: Unclassified
Component: Enhancement/Feature Requests (show other bugs)
Hardware: All Linux
: High enhancement
Assignee: Portage team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-09-17 10:21 UTC by Wolfram Schlich (RETIRED)
Modified: 2008-09-17 13:29 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Wolfram Schlich (RETIRED) gentoo-dev 2008-09-17 10:21:10 UTC
Please add support for package.keywords in profiles to Portage 2.2 :)

Reason: I want to be able to completely avoid using /etc/portage on
machines that get their packages from a BINHOST/buildserver.

I'm using a custom profile on the BINHOST/buildserver based on a
Gentoo profile. That profile is automagically added to the local
Portage tree (upstream/Gentoo + my profile) and synced from the
BINHOST clients.

When I want to build a package on the BINHOST/buildserver
for an ebuild that is in ~arch, I have to add that one to
package.keywords inside the corresponding buildroot (I currently
have one x86 and one amd64 buildroot) on the BINHOST/buildserver
*and* to package.keywords on the BINHOST client.

What I want instead is add it to package.keywords in my profile
and just "be done" with that (of course, the clients still need
to re-sync their Portage tree but that is already necessary for
other things like metadata/glsa for example).

Comments, please :)

Thanks!
Comment 1 Wolfram Schlich (RETIRED) gentoo-dev 2008-09-17 11:31:30 UTC
Currently my profiles/ directory looks like this:

profiles/categories
profiles/repo_name
profiles/use.desc
profiles/use.local.desc
profiles/somecompany
profiles/somecompany/amd64
profiles/somecompany/amd64/2008.0
profiles/somecompany/amd64/2008.0/server
profiles/somecompany/amd64/2008.0/server/parent
# contains this:
# /usr/portage/profiles/hardened/linux/amd64/2008.0/server
# ../../../targets/server
profiles/somecompany/x86
profiles/somecompany/x86/2008.0
profiles/somecompany/x86/2008.0/server
profiles/somecompany/x86/2008.0/server/parent
# ^^^ contains this:
# /usr/portage/profiles/hardened/linux/x86/2008.0/server
# ../../../targets/server
profiles/somecompany/targets
profiles/somecompany/targets/server
profiles/somecompany/targets/server/make.defaults
# ^^^ contains everything I used to put in make.conf before
profiles/somecompany/targets/server/package.mask
profiles/somecompany/targets/server/package.provided
profiles/somecompany/targets/server/package.use
profiles/somecompany/targets/server/package.use.force
profiles/somecompany/targets/server/package.use.mask
profiles/somecompany/targets/server/packages
profiles/somecompany/targets/server/packages.build
profiles/somecompany/targets/server/profile.bashrc
profiles/somecompany/targets/server/use.defaults.DEPRECATED
profiles/somecompany/targets/server/use.force
profiles/somecompany/targets/server/use.mask
profiles/somecompany/targets/server/virtuals

(use.defaults.DEPRECATED is just some sort of 'reminder' for myself)

/etc/make.profile on the BINHOST clients either points to
profiles/somecompany/amd64/2008.0/server or
profiles/somecompany/x86/2008.0/server.

So, the only thing I'm missing here is package.keywords :)
Comment 2 Zac Medico gentoo-dev 2008-09-17 13:29:36 UTC

*** This bug has been marked as a duplicate of bug 55321 ***