| 1 |
YES! (thanks, Eric), |
| 2 |
|
| 3 |
to chime in on this thread... |
| 4 |
|
| 5 |
Most uses of Gentoo are mature, bleeding edge folk who -should- know the |
| 6 |
danger of blindly "emerging" -u world (if not, they need to relearn the |
| 7 |
*NIX tradition of RTFM). |
| 8 |
|
| 9 |
But I too would like to see a way of "locking down" my "unmasks". For |
| 10 |
example, I've been compiling everything using BINUTILS-2.12 (?) for weeks |
| 11 |
now without problems or difficulties. It's a royal pain, however, to have |
| 12 |
to edit my ../profiles/default-1.0/packages after every emerge. |
| 13 |
|
| 14 |
I'll state openly that I'm not a programmer, so I have no idea how |
| 15 |
difficult the aforementioned would be, but it sure would be *nice* to have |
| 16 |
some mask control built into Portage. |
| 17 |
|
| 18 |
Best, |
| 19 |
/tom |
| 20 |
|
| 21 |
--On Friday, June 07, 2002 15:27:42 -0400 Eric Thibeault Jolin |
| 22 |
<irise-lenoir@×××××××××.ca> wrote: |
| 23 |
|
| 24 |
> |
| 25 |
> Portage works like a charm, but it is a chore to use package.masked stuff |
| 26 |
> and update often. I want a /etc/package.mask file that doesn't get |
| 27 |
> modified by portage and overrides /usr/portage/profile/package.mask. I |
| 28 |
> also want the ability to write something like "! |
| 29 |
> >=gnome-base/gnome-2.0.0_beta5" to force unmasking a package. But user |
| 30 |
> masking will be nice too, like to force not installing jdk 1.4 on |
| 31 |
> "emerge--update world" or to "remove nautilus from gnome-base", at least |
| 32 |
> in effect. When I said portage shouldn't tamper with it, a possible |
| 33 |
> exception might be when a package forced unmasked in /etc is permanently |
| 34 |
> removed from /usr/portage/profile/package.mask, it might be good to |
| 35 |
> remove it from /etc/package.mask (respecting config protection, of |
| 36 |
> course). |
| 37 |
> |
| 38 |
> On the other point of view, a /etc/package.protect file might be useful |
| 39 |
> to manually protect a package or version of package from being removed by |
| 40 |
> "emerge clean". |
| 41 |
> |
| 42 |
> As I said, it already works wonders, but these small changes and it will |
| 43 |
> be perfect! Okay, maybe not... almost perfect. |
| 44 |
> |
| 45 |
> _______________________________________________ |
| 46 |
> gentoo-dev mailing list |
| 47 |
> gentoo-dev@g.o |
| 48 |
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev |
Archives