38402 – configuration file to unmask an ebuild permanently

Bug 38402 - configuration file to unmask an ebuild permanently

Summary: configuration file to unmask an ebuild permanently

Status:	RESOLVED DUPLICATE of bug 5622

Alias:	None

Product:	Portage Development
Classification:	Unclassified
Component:	Core - Configuration (show other bugs)
Hardware:	All Linux

Importance:	High enhancement (vote)
Assignee:	Portage team

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2004-01-16 07:22 UTC by Timo Stöckigt
Modified:	2005-07-17 13:06 UTC (History)
CC List:	0 users

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Timo Stöckigt 2004-01-16 07:22:48 UTC

It would be good to have a new file, where I can store packages that I want to have always bleeding-edge. For example I want always the newest KDE version but the rest of my system shall stay relative stable.

Suggestion: /usr/portage/profiles/package.unmask.permanently
# comment
kde
ck-sources

Portage will install then always the newest available ebuilds and I don't have to tweak always my package.mask-file.

Reproducible: Always
Steps to Reproduce:
1.
2.
3.

Comment 1 David Westley 2004-01-16 07:29:04 UTC

With Portage 2.0.50 you can put a line like 'kde-base/kde' in /etc/portage/package.unmask and it will unmask ALL versions of the package but still respects ACCEPT_KEYWORDS and /etc/portage/package.keywords

Comment 2 Marius Mauch (RETIRED) gentoo-dev

2004-01-16 07:37:32 UTC

/etc/portage/package.unmask
/etc/portage/package.keywords

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