From: Thomas Sachau <tommy@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Amount of useflags enabled by default
Date: Sat, 24 Oct 2009 18:35:50 +0200 [thread overview]
Message-ID: <4AE32CE6.6060104@gentoo.org> (raw)
In-Reply-To: <200910241355.35305.ali_bush@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 2472 bytes --]
Alistair Bush schrieb:
>> Hi,
>>
>> i would like to start a discussion about reducing the amount of
>> default-enabled USE flags in profiles, especially in inherited basic
>> profiles.
>
> Sounds like a reasonable idea to me, for the base profiles at least.
Sure. If we have a desktop/kde subprofile, noone should complain, if that profile enables kde
specific USE flags. On the other hand, if i just want a desktop without kde, i dont want to be
forced to either choose a none-desktop profile and enable many USE flags by hand or using the
desktop profile and disabling many USE flags by hand.
>
>> In addition, i see a trend to enabled more more more USE flags (either over
>> profiles or via IUSE +flag). Whats the reason for forcing a big load of
>> default enabled USE flags on every user including more dependencies, more
>> compile time, more wasted disk space and more possible vulnerabilities
>> except some users, who complain about a missing feature and are not able
>> to think and enable a USE flag for that feature?
>>
>
> ".... who complain about a enabled feature and are not able to think and
> disable a USE flag for that feature?"
>
> What a couple of changes make....
I dont mind, if a flag is really usefull and requested by a big majority of the users. But as Gentoo
is about choice, the minority should be able to easily choose something else, e.g. by a less
heavyweight profile. If a majority of mplayer users want to be able to play audio files, i dont mind
to disable it for myself, if i dont want it. But on the other hand shouldnt a handfull of users be
able to dictate the enabled and disabled USE flags for many other users, which might have a
different interest.
>
> It would be nice if we actually documented why they were enabled. Does the
> use flag enable significant functionality that would otherwise make the software
> less useful.
Documentation is always usefull. One should also check the additional overhead of the USE flag.
>
> I believe we should be trying to find a nice 'middle of the road' balance. DE
> "related" use flags should be enabled in profiles ( unless of coarse they
> package is already DE related e.g if a kde package has a use flag for kde's
> sound system, this could be enabled at a package level while a package with a
> kde use flag should not default enable it.).
I aggree.
--
Thomas Sachau
Gentoo Linux Developer
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 316 bytes --]
next prev parent reply other threads:[~2009-10-24 16:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-23 16:56 [gentoo-dev] Amount of useflags enabled by default Thomas Sachau
2009-10-23 19:32 ` Sebastian Pipping
2009-10-24 16:14 ` Thomas Sachau
2009-10-23 19:54 ` Petteri Räty
2009-10-24 16:03 ` Pacho Ramos
2009-10-24 16:24 ` Thomas Sachau
2009-10-24 19:38 ` William Hubbs
2009-10-24 0:55 ` Alistair Bush
2009-10-24 16:35 ` Thomas Sachau [this message]
2009-11-06 23:40 ` Ed W
2009-11-07 7:46 ` [gentoo-dev] " Duncan
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=4AE32CE6.6060104@gentoo.org \
--to=tommy@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