From: Pacho Ramos <pacho@condmat1.ciencias.uniovi.es>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Amount of useflags enabled by default
Date: Sat, 24 Oct 2009 18:03:42 +0200 [thread overview]
Message-ID: <1256400222.29541.3.camel@localhost.localdomain> (raw)
In-Reply-To: <4AE209E6.7020707@gentoo.org>
El vie, 23-10-2009 a las 22:54 +0300, Petteri Räty escribió:
> Thomas Sachau wrote:
> >
> > 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?
> >
>
> One possible reason is that our packages should follow upstream policy
> and maybe upstreams usually like to keep things enabled rather than
> disabled.
>
> Regards,
> Petteri
>
>
I don't see any problem in enabling some USE flags by default but,
maybe, would be interesting to have a place where people could consult
why some USEs are enabled and, specially, disabled by default.
The problem is where to write that information :-/ (into the ebuild,
into metadata file...)
Best regards
next prev parent reply other threads:[~2009-10-24 16:03 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 [this message]
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
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=1256400222.29541.3.camel@localhost.localdomain \
--to=pacho@condmat1.ciencias.uniovi.es \
--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