From: Rigo <rigo@home.nl>
To: gentoo-dev <gentoo-dev@gentoo.org>
Subject: Re: [gentoo-dev] Overriding package mask
Date: 18 Aug 2002 11:43:05 +0200 [thread overview]
Message-ID: <1029663785.11198.17.camel@lappy.rogi.biz> (raw)
In-Reply-To: <1029663627.11533.14.camel@lappy.rogi.biz>
Hmmm, Just saw this was suggestion no. 2 in Bugzilla....Seems I have to
spend EVEN MORE time overthere ;-D !
Never Mind !
Rigo
Op zo 18-08-2002, om 11:40 schreef Rigo:
> Op zo 18-08-2002, om 08:57 schreef Jonathan Kelly:
> > On 18 Aug 2002 16:31:21 +1000
> > Troy Dack <troy@tkdack.com> wrote:
> >
> > > On Sun, 2002-08-18 at 14:04, Jonathan Kelly wrote:
> > > > I beg to differ ... I did this with media-gfx/povray and after every
> > > > "emerge sync" I get ....
> > > > # emerge -pu povray
> > >
> > > My apologies, I thought that the local ebuilds were NOT checked against
> > > packages.mask.
> > >
> > > I've just tried the same thing as you, with the same results.
> > >
> > > It would make sense (to me anyway) if the local ebuilds in
> > > $PORTDIR_OVERLAY were *NOT* checked against packages.mask, that way us
> > > end users could assist the developers by simply dropping masked ebuilds
> > > into our local tree and then testing them. Sure it means that there is
> > > duplication and some extra hard drive space taken up, but ebuilds aren't
> > > that big. Also for those wishing to test ebuilds it would be a
> > > conscious decision to place a masked ebuild in your local tree.
> >
> > I think that is a logical and great idea.
>
> Wouldn't it also be nice if settings in
> $PORTDIR_OVERLAY/profiles/package.mask overrule settings in
> $PORTDIR/profiles/package.mask ? This way directories could stay in
> $PORTDIR and you don't have to keep worrying about changin' package.mask
> time & time again.
>
> Ex:
>
> lappy # diff /usr/portage/profiles/package.mask
> /root/package.mask.2|grep povray
>
> < #=media-gfx/povray-3.50a
> > =media-gfx/povray-3.50a
>
>
> Just a thought,
>
> Rigo
>
> >
> > Cheers.
> > Jonathan Kelly.
> > _______________________________________________
> > gentoo-dev mailing list
> > gentoo-dev@gentoo.org
> > http://lists.gentoo.org/mailman/listinfo/gentoo-dev
>
>
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev
next prev parent reply other threads:[~2002-08-18 12:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-16 22:28 [gentoo-dev] Overriding package mask Sebastian Werner
2002-08-16 22:42 ` mike
2002-08-16 23:08 ` Troy Dack
2002-08-17 16:13 ` Sebastian Werner
2002-08-18 4:04 ` Jonathan Kelly
2002-08-18 6:31 ` Troy Dack
2002-08-18 6:57 ` Jonathan Kelly
2002-08-18 9:40 ` Rigo
2002-08-18 9:43 ` Rigo [this message]
2002-08-18 16:26 ` Jon Nelson
2002-08-18 17:26 ` mike
2002-08-18 8:13 ` Fredrik Jagenheim
2002-08-18 11:12 ` Troy Dack
-- strict thread matches above, loose matches on Subject: below --
2002-08-18 6:54 Thomas Beaudry
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1029663785.11198.17.camel@lappy.rogi.biz \
--to=rigo@home.nl \
--cc=gentoo-dev@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox