From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] use.force support
Date: Wed, 15 Jun 2005 09:52:03 -0400 [thread overview]
Message-ID: <1118843523.14164.16.camel@cgianelloni.nuvox.net> (raw)
In-Reply-To: <42AF9765.8090800@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1225 bytes --]
On Tue, 2005-06-14 at 19:50 -0700, Donnie Berkholz wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Sven Wegener wrote:
> > On Mon, Jun 13, 2005 at 06:56:43PM -0400, Ned Ludd wrote:
> >
> >>I'm in favor of this. Would you mind calling it package.autouse,
> >>package.use.auto or are you set on .force?
> >
> >
> > As Mike already wrote those names are too confusing with the automatic
> > activated USE flags. We already had some suggestions in this thread, but
> > none of them actually matched the purpose of the file. At least in my
> > opinion. use.force matches it best, but the "force" part is a quite hard
> > term. How about use.profile? Because these USE flags are activated or
> > needed by the profile.
>
> How about use.required, since they're required by the profile?
I like this much better. It gives the user an obvious sense of the
purpose of the file/USE flags. It also doesn't give the impression of
"forcing" something on people, but rather to say that "these need to be
here for proper functionality of this profile", which seems to be less
intrusive.
--
Chris Gianelloni
Release Engineering - Strategic Lead/QA Manager
Games - Developer
Gentoo Linux
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-06-15 13:57 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-13 14:40 [gentoo-dev] use.force support Sven Wegener
2005-06-13 16:47 ` Harald van Dijk
2005-06-13 18:23 ` Sven Wegener
2005-06-14 5:42 ` Harald van Dijk
2005-06-13 18:28 ` Simon Stelling
2005-06-13 19:56 ` Dan Meltzer
2005-06-13 20:40 ` Kito
2005-06-13 20:54 ` Sven Wegener
2005-06-14 22:34 ` Sami Näätänen
2005-06-13 22:43 ` Sven Wegener
2005-06-14 2:17 ` Kumba
2005-06-13 20:50 ` Sven Wegener
2005-06-13 21:08 ` Alec Warner
2005-06-13 21:27 ` Diego 'Flameeyes' Pettenò
2005-06-13 22:12 ` Mike Frysinger
2005-06-14 14:02 ` Jan Kundrát
2005-06-13 21:38 ` Sven Wegener
2005-06-14 17:46 ` Alec Warner
2005-06-14 17:54 ` Diego 'Flameeyes' Pettenò
2005-06-15 1:16 ` Sven Wegener
2005-06-13 22:56 ` Ned Ludd
2005-06-13 23:29 ` Mike Frysinger
2005-06-15 1:26 ` Sven Wegener
2005-06-15 2:50 ` Donnie Berkholz
2005-06-15 9:03 ` [gentoo-dev] " Duncan
2005-06-15 23:17 ` Georgi Georgiev
2005-06-16 6:04 ` [gentoo-dev] " Duncan
2005-06-15 11:43 ` [gentoo-dev] " Sven Wegener
2005-06-20 0:32 ` Jason Stubbs
2005-06-15 13:52 ` Chris Gianelloni [this message]
2005-06-14 2:43 ` Jason Wever
2005-06-14 9:21 ` Diego 'Flameeyes' Pettenò
2005-06-16 13:30 ` Herbie Hopkins
2005-06-15 10:16 ` Thomas de Grenier de Latour
2005-06-15 11:53 ` Sven Wegener
2005-06-15 13:51 ` Alec Warner
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=1118843523.14164.16.camel@cgianelloni.nuvox.net \
--to=wolf31o2@gentoo.org \
--cc=gentoo-dev@lists.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