On 8/13/07, Nathan Smith <[EMAIL PROTECTED]> wrote:
> On 8/12/07, Alec Warner <[EMAIL PROTECTED]> wrote:
> > On 8/11/07, Rumi Szabolcs <[EMAIL PROTECTED]> wrote:
> > > Hello!
> > >
> > > I've got a couple of suggestions for emerge:
> > >
> > > 1.) I apparently cannot exclude one or two packages from a large
> > > emerge action. For example if I say 'emerge -upv world' or
> > > 'emerge -Dupv xorg-x11' it may pull in some large updates I do
> > > not want to do, like gcc or glibc but there is no such thing as
> > > an exclusion list like 'emerge -Dupv xorg-x11 --except gcc glibc'
> > > to stop it from emerging these but let it do everything else.
> >
> > add them to /etc/portage/package.mask
> That and that package.provided hack would work, but they are not
> nearly as nice as the feature Rumi suggested would be. I have run
> into the same frustration in the past and I would find that feature
> quite useful.
>
> I suppose this comes down to weighing the utility of such a feature
> against the amount of effort which would go into adding it to Portage.
> I do not know enough to make an informed decision on that point.
> Still, I think it is worth discussing rather than dismissing it with a
> hack.
Its trivial to implement, but I think its a long standing decision of
the portage team to not do it.
We typically don't write things for emerge that touch your
/etc/portage files (aside from updates/)
We also don' t like one-offs. We used to recommend people do stuff like
"ACCEPT_KEYWORDS=~x86 emerge foo"
or
"USE='foo bar baz' emerge foo"
which both suck because the next time you use emerge your settings are lost.
You should be serializing your options into the configuration
(package.{mask,provided}) rather than doing one-off command line
things.
Echoing crap to to package.mask or running a utility that does it is
pretty easy imho.
-Alec
--
[EMAIL PROTECTED] mailing list
