On 2010-11-17, Neil Bothwick <n...@digimed.co.uk> wrote:
> On Wed, 17 Nov 2010 16:48:30 +0000, David W Noon wrote:
>
>> >Surely what `./configure` does if I don't make any choice about its
>> >compilation option is to be considered a "default"?
>>
>> Gentoo ebuilds do not run ./configure without options, unless there are
>> no options available.
That's irrelevent. You said upstream doesn't come with a "default"
configuration. We're saying it does, and that it's defined by the
default options in the configure script. Even if Gentoo doesn't use
that default configuration it doens't meant that it doesn't exist.
> No, but they generally set the USE defaults to give the same settings
> as running ./configure with none. In other words, they are following
> the upstream defaults.
We seem to be going around in circles. :)
The merits of using HAL for Xorg config aside, I am still curious
about where the "default" configuration for a package comes from. Is
there a written policy somewhere that tells devs how to set the
default USE flags?
--
Grant Edwards grant.b.edwards Yow! I'm having a MID-WEEK
at CRISIS!
gmail.com
