From: Jason Stubbs <jasonbstubbs@mailandnews.com>
To: gentoo-portage-dev@gentoo.org
Subject: Re: [gentoo-portage-dev] The purpose of USE flags
Date: Tue, 16 Dec 2003 18:38:33 +0900 [thread overview]
Message-ID: <200312161838.33650.jasonbstubbs@mailandnews.com> (raw)
In-Reply-To: <20031214232302.34466a1b.genone@gentoo.org>
On Monday 15 December 2003 07:23, Marius Mauch wrote:
> personally I really dislike this proposal as it adds a lot of complexity
> for functionality that would rarely be used.
Agreed there.
> Also IMO USE flags should not prevent the installation of a package, that's
> the job of masking.
Many users often get frustrated by the fact that they have specified "-arts",
for example, but still get arts installed. If USE flags specified optional
and intrinsic functionality, this would not be hard to implement and would be
much more intuitive than package masking.
On the other hand, if the current package masking was made more intuitive and
advertised, there probably wouldn't be anywhere near as many users as there
are complaining.
Either way, I think that having ebuilds specifiy their intrinsic functionality
through USE flags or such some construct has many benefits.
--
Regards,
Jason Stubbs
--
gentoo-portage-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-12-16 9:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-12 19:27 [gentoo-portage-dev] The purpose of USE flags Jason Stubbs
2003-12-14 19:24 ` Sami Näätänen
2003-12-14 22:23 ` Marius Mauch
2003-12-16 9:38 ` Jason Stubbs [this message]
2003-12-16 17:11 ` Sami Näätänen
2003-12-16 19:59 ` Marius Mauch
2003-12-16 21:50 ` Sami Näätänen
2003-12-16 22:23 ` Jason Stubbs
2003-12-17 0:10 ` Marius Mauch
2003-12-17 7:11 ` Jason Stubbs
2003-12-16 21:36 ` Pieter Van den Abeele
2003-12-16 22:23 ` Paul de Vrieze
2003-12-16 22:53 ` Pieter Van den Abeele
2003-12-16 9:19 ` Jason Stubbs
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=200312161838.33650.jasonbstubbs@mailandnews.com \
--to=jasonbstubbs@mailandnews.com \
--cc=gentoo-portage-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