public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Petteri Räty" <betelgeuse@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Unused ebuild built_with_use cleanup
Date: Fri, 09 Oct 2009 16:38:11 +0300	[thread overview]
Message-ID: <4ACF3CC3.3090901@gentoo.org> (raw)
In-Reply-To: <200910090217.43072.patrick@gentoo.org>

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

Patrick Lauer wrote:
> 
> And that's with all the "forced" migrations for features like use-deps or the 
> removal of built_with_use. So unless there's some "strongly needed" features 
> there's no need for it. I can't remember any feature in the EAPI 3 list that 
> really looked useful to me, so not adding it now now now doesn't bother me at 
> all. Just causes more confusion for no real benefit. So who cares if it is 
> delayed by a few timeunits, there's much more important stuff to do.
> 

Here's two features that by themselves are important enough to get EAPI
3 implemented. Using pkg_pretend it should be possible to eliminate
expected dies from build time and as such improving user experience. An
example is two use flags that conflict with each other. Use dependency
defaults make the life of ebuild writers easier as you don't need to be
careful with version restrictions any more if you have a case where
something has been on by default and then becomes a use flag for
example. This should eliminate cases like causing glibc downgrade in the
depgraph by being careless.

Regards,
Petteri


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

  reply	other threads:[~2009-10-09 13:38 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-29 13:32 [gentoo-dev] Unused ebuild built_with_use cleanup Petteri Räty
2009-10-07 11:21 ` Marijn Schouten (hkBst)
2009-10-08 21:29   ` Petteri Räty
2009-10-07 11:54 ` Stelian Ionescu
2009-10-08 21:34   ` Petteri Räty
2009-10-08 22:03     ` Jeremy Olexa
2009-10-08 22:22       ` Petteri Räty
2009-10-09  0:17         ` Patrick Lauer
2009-10-09 13:38           ` Petteri Räty [this message]
2009-10-08 22:25     ` Tomáš Chvátal
2009-10-09 13:41       ` Petteri Räty
2009-10-24 12:32 ` [gentoo-dev] Re: [gentoo-dev-announce] " Petteri Räty
2009-10-24 20:29   ` James Cloos
2009-10-25  9:48     ` Petteri Räty
2009-10-26 23:21       ` James Cloos
2009-10-27 13:12         ` Petteri Räty
2009-10-27  6:07       ` Ryan Hill
2009-10-27  7:02         ` Mike Frysinger
2009-10-27 13:09           ` Petteri Räty
2009-10-27 13:46             ` Mike Frysinger
2009-10-27 18:46               ` Petteri Räty
2009-10-28  2:31                 ` [gentoo-dev] " Mike Frysinger
2009-10-28  9:51                   ` Petteri Räty
2009-10-28 11:11                     ` Alexis Ballier
2009-10-30  2:29                     ` Doug Goldstein

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=4ACF3CC3.3090901@gentoo.org \
    --to=betelgeuse@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