From: Jon Nelson <jnelson@jamponi.net>
To: Jonathan Kelly <j0n@tpg.com.au>
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Overriding package mask
Date: Sun, 18 Aug 2002 11:26:44 -0500 [thread overview]
Message-ID: <20020818112644.21a98116.jnelson@jamponi.net> (raw)
In-Reply-To: <20020818165734.6029f4bc.j0n@tpg.com.au>
On Sun, 18 Aug 2002 16:57:34 +1000
Jonathan Kelly <j0n@tpg.com.au> wrote:
> > It would make sense (to me anyway) if the local ebuilds in
> > $PORTDIR_OVERLAY were *NOT* checked against packages.mask, that way us
..
> I think that is a logical and great idea.
I disgree. I think it's a hack that doesn't really solve the problem at
hand, which is "supplementary" package masking, using the package
mask in /usr/portage as the 'canonical' package mask and then using
a second package mask to over ride that.
PORTDIR_OVERLAY is there for just one reason, to provide *local*
ebuilds. If the behavior of ebuilds is different here, that is an
inferred behavior and not a logical one.
package masking and ebuilds are separate, keep their interfaces
separate.
--
Pound for pound, the amoeba is the most vicious animal on earth.
Jon Nelson <jnelson@jamponi.net>
C and Python Code Gardener
next prev parent reply other threads:[~2002-08-18 16:26 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
2002-08-18 16:26 ` Jon Nelson [this message]
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=20020818112644.21a98116.jnelson@jamponi.net \
--to=jnelson@jamponi.net \
--cc=gentoo-dev@gentoo.org \
--cc=j0n@tpg.com.au \
/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