public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Kito <kito@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] use.force support
Date: Mon, 13 Jun 2005 15:40:34 -0500	[thread overview]
Message-ID: <66C5138E-6E3A-432E-90B5-9E8F798009DC@gentoo.org> (raw)
In-Reply-To: <46059ce10506131256c014866@mail.gmail.com>


On Jun 13, 2005, at 2:56 PM, Dan Meltzer wrote:

> Seems like use.force might be a bad name..... when I first read the
> email, and saw use.force, the first thing that came to mind was
> "gentoo forcing something?" and even after reading the email, I
> wouldn't expect to be able to override something that was "forced."
> I'm not sure what a better name would be, but I think there may be
> one...
>
> also, wouldn't the override be in use.unforce? >_<

what about just a use.env?

>
> On 6/13/05, Simon Stelling <blubb@gentoo.org> wrote:
>
>> Sven Wegener wrote:
>>
>>> We just had a short discussion over in #gentoo-portage and the  
>>> idea of
>>> an use.force file for profiles came up. It allows us to force  
>>> some USE
>>> flags to be turned on for a profile. It's not possible to disable  
>>> this
>>> flag by make.conf, the environment or package.use. But we would  
>>> not be
>>> Gentoo, if we don't leave a backdoor. You can disable the flag by
>>> putting -flag in /etc/portage/profile/use.force if you really  
>>> need to.
>>> Same goes for sub-profiles that need to disable this flag.
>>>
>>
>> Yay!
>>
>>
>>> I gues use.force has some other places where it is useful. Like the
>>> default-darwin profiles which use ARCH="ppc" and USE="ppc-macos"  
>>> but the
>>> ppc-macos flag can be removed by using USE="-ppc-macos" in the
>>> environment. Or selinux profiles, to force the selinux flag to be  
>>> turned
>>> on.
>>>
>>
>> It'll be also very useful for the amd64 profiles as in 2005.0 the use
>> flag 'multilib' is disabled but multilib-support is forced. (There  
>> are
>> no-multilib-profiles though.)
>>
>>
>>> Comments?
>>>
>>
>> I consider use.force very useful, it'll finally make all the amd64  
>> users
>> stop asking themselves why the documenation says they will get  
>> multilib
>> but the use flag is disabled, so please, go ahead implementing it.
>>
>> Regards,
>>
>> blubb
>>
>> --
>> Simon Stelling
>> Gentoo/AMD64 Operational Co-Lead
>> blubb@gentoo.org
>> --
>> gentoo-dev@gentoo.org mailing list
>>
>>
>>
>
> -- 
> gentoo-dev@gentoo.org mailing list
>
>

-- 
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2005-06-13 20:40 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 [this message]
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
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=66C5138E-6E3A-432E-90B5-9E8F798009DC@gentoo.org \
    --to=kito@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