public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] should we do an EAPI bump now with features that are already implemented?
Date: Tue, 10 Jul 2007 01:17:04 -0400	[thread overview]
Message-ID: <200707100117.04889.vapier@gentoo.org> (raw)
In-Reply-To: <20070709232619.7d7052b5@snowflake>

[-- Attachment #1: Type: text/plain, Size: 673 bytes --]

On Monday 09 July 2007, Ciaran McCreesh wrote:
> As for IUSE defaults... There were objections against that feature on
> the grounds that it's unnecessary and increased maintenance. Do they
> really offer any benefit over package.use?

where ?  i have yet to see an objection to IUSE defaults and plenty of 
support.  in fact, the exact opposite makes sense: it *decreases* 
maintenance.  time and again having information split between an ebuild and 
the profiles/ directory has resulted in bit rot.  having all the information 
in the ebuild allows for trivial changes on a per-ebuild basis and not 
needing to update multiple files in unrelated trees.
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 827 bytes --]

  reply	other threads:[~2007-07-10  5:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-09 22:15 [gentoo-dev] [RFC] should we do an EAPI bump now with features that are already implemented? Zac Medico
2007-07-09 22:26 ` Ciaran McCreesh
2007-07-10  5:17   ` Mike Frysinger [this message]
2007-07-09 22:28 ` Petteri Räty
2007-07-10 16:01   ` Zac Medico
2007-07-10 16:50     ` Petteri Räty
2007-07-10 17:14       ` Ciaran McCreesh
2007-07-10 17:26         ` Petteri Räty
2007-07-10 17:32           ` Ciaran McCreesh
2007-07-10 17:37             ` Petteri Räty
2007-07-10  6:14 ` [gentoo-dev] " Stefan Schweizer
2007-07-10  8:08   ` Marius Mauch

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=200707100117.04889.vapier@gentoo.org \
    --to=vapier@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