public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Pacho Ramos <pacho@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Collecting items for EAPI 6
Date: Fri, 29 Mar 2013 11:31:07 +0100	[thread overview]
Message-ID: <1364553067.2169.0.camel@belkin4> (raw)
In-Reply-To: <20130328191559.39e66934@pomiocik.lan>

El jue, 28-03-2013 a las 19:15 +0100, Michał Górny escribió:
> Hello,
> 
> As discussed with ulm, I'd like to start a thread for collecting
> initial items for EAPI 6. Preferably items which are either almost
> ready or are easy to implement and are non-controversial. In other
> words, thing which are practically ready to get on the actual list.
> 
> As usual, each item should have a corresponding 'Future EAPI' bug which
> blocks the tracker [1].
> 
> [1]:https://bugs.gentoo.org/show_bug.cgi?id=future-eapi
> 
> 
> My propositions:
> 
> a) for improving self-consistency of EAPI (high priority):
> 
> - #463586: move get_libdir to EAPI (since it is used in econf).
> 
> - #459692: split the doc-installation part of default_src_install
>   (e.g. as einstalldocs).
> 
> - #451938: provide a 'die' variant respecting 'nonfatal' (to implement
>   custom helpers respecting 'nonfatal').
> 
> 
> b) for improving ebuild & eclass development:
> 
> - #449862: tidy up IUSE checking.
> 
> - #449806: support using DOCS to append to the standard document list.
> 
> - #431340: allow bash-4.2 (may require additional policy restrictions).
> 
> - #273101: explicit variable for no. of parallel jobs (rather than
>   hacking MAKEOPTS).
> 

I would also add, if possible:
https://bugs.gentoo.org/show_bug.cgi?id=449862 -> Suggest to specify a
way to query for values in IUSE



  parent reply	other threads:[~2013-03-29 10:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-28 18:15 [gentoo-dev] Collecting items for EAPI 6 Michał Górny
2013-03-29  9:20 ` Tomáš Chvátal
2013-03-29 10:31 ` Pacho Ramos [this message]
2013-03-29 17:54 ` Andreas K. Huettel
2013-03-29 17:57   ` Ciaran McCreesh
2013-03-29 18:17     ` Andreas K. Huettel
2013-03-30 18:39 ` Christoph Junghans
2013-03-30 18:50   ` Ciaran McCreesh

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=1364553067.2169.0.camel@belkin4 \
    --to=pacho@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