1 |
Daniel Robbins wrote: |
2 |
> |
3 |
> Developers, |
4 |
> |
5 |
> I just updated the current version of Portage on CVS (portage-1.5_pre10). |
6 |
> This version of portage seems to be working well for Achim, and now has |
7 |
> an additional new feature. |
8 |
> |
9 |
> The /usr/portage/profiles/package.mask file can now be used to *eliminate* |
10 |
> packages for consideration by the auto-build system. It's really useful |
11 |
> if you are adding experimental and not-quite-working packages to portage. |
12 |
> Simply add a dependency line to /usr/portage/package.mask that matches the particular |
13 |
> ebuild you'd like to mark as "not ready for others". Each dependency should |
14 |
> appear on its own line, and "# style" comments are allowed as long as the |
15 |
> line begins with a "#". Here's an example package.mask file: |
16 |
> |
17 |
> #sys-apps/bash-2.05 is experimental (not really, this is just an example) |
18 |
> =sys-apps/bash-2.05 |
19 |
> |
20 |
> #sys-apps/foo (all versions) should *not* be available to end-users |
21 |
> sys-apps/foo |
22 |
|
23 |
Daniel, I have a question, why is it easier to add a new file |
24 |
(package.mask) that excludes packages |
25 |
instead of using the already existing packages file for masquerading |
26 |
(oposite of package.mask)? |
27 |
|
28 |
BTW: it seems that the new readline version (4.2, required for |
29 |
bash-2.05) is not 100% compatible to |
30 |
4.1. I tried to compile postgress yesterday and it only works with 4.1 |
31 |
but fails with 4.2. |
32 |
So it is a good idea too keep bash-2.05 in package.mask. |
33 |
|
34 |
achim~ |
35 |
|
36 |
> |
37 |
> Right now, "=sys-apps/bash-2.05" is in the package.mask file as a placeholder. |
38 |
> As soon as Achim gets the new version of Portage on his system and tests out |
39 |
> the package.mask feature, it'll be removed :) If you merge the brand-new |
40 |
> version of portage-1.5_pre10, you'll find that for the time being, bash-2.05 |
41 |
> will not be found by "emerge". |
42 |
> |
43 |
> However, you can still install masked packages using ebuild. |
44 |
> |
45 |
> All developers should now use package.mask as a way to ensure that end-users |
46 |
> don't accidentally auto-merge experimental ebuilds. |
47 |
> |
48 |
> Best Regards, |
49 |
> |
50 |
> -- |
51 |
> Daniel Robbins <drobbins@g.o> |
52 |
> President/CEO http://www.gentoo.org |
53 |
> Gentoo Technologies, Inc. |
54 |
> |
55 |
> _______________________________________________ |
56 |
> gentoo-dev mailing list |
57 |
> gentoo-dev@g.o |
58 |
> http://www.gentoo.org/mailman/listinfo/gentoo-dev |