Gentoo Archives: gentoo-dev

From: Daniel Robbins <drobbins@g.o>
To: gentoo-dev@g.o
Subject: [gentoo-dev] package.mask
Date: Fri, 13 Apr 2001 15:18:46
1 Developers,
3 I just updated the current version of Portage on CVS (portage-1.5_pre10).
4 This version of portage seems to be working well for Achim, and now has
5 an additional new feature.
7 The /usr/portage/profiles/package.mask file can now be used to *eliminate*
8 packages for consideration by the auto-build system. It's really useful
9 if you are adding experimental and not-quite-working packages to portage.
10 Simply add a dependency line to /usr/portage/package.mask that matches the particular
11 ebuild you'd like to mark as "not ready for others". Each dependency should
12 appear on its own line, and "# style" comments are allowed as long as the
13 line begins with a "#". Here's an example package.mask file:
15 #sys-apps/bash-2.05 is experimental (not really, this is just an example)
16 =sys-apps/bash-2.05
18 #sys-apps/foo (all versions) should *not* be available to end-users
19 sys-apps/foo
21 Right now, "=sys-apps/bash-2.05" is in the package.mask file as a placeholder.
22 As soon as Achim gets the new version of Portage on his system and tests out
23 the package.mask feature, it'll be removed :) If you merge the brand-new
24 version of portage-1.5_pre10, you'll find that for the time being, bash-2.05
25 will not be found by "emerge".
27 However, you can still install masked packages using ebuild.
29 All developers should now use package.mask as a way to ensure that end-users
30 don't accidentally auto-merge experimental ebuilds.
32 Best Regards,
34 --
35 Daniel Robbins <drobbins@g.o>
36 President/CEO
37 Gentoo Technologies, Inc.


Subject Author
Re: [gentoo-dev] package.mask (Achim Gottinger)