public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ulrich Mueller <ulm@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: [gentoo-project] Re: [gentoo-dev-announce] Call For Agenda Items - 10 Jun 2014
Date: Thu, 29 May 2014 15:56:01 +0200	[thread overview]
Message-ID: <21383.15473.683811.968431@a1i15.kph.uni-mainz.de> (raw)
In-Reply-To: <CAGfcS_nydQyxTBw1h0J37o2k7hTRDCdEyy=z=f02geLtauy++Q@mail.gmail.com>

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

>>>>> On Mon, 26 May 2014, Rich Freeman wrote:

> The next Gentoo Council meeting will be on 10 Jun 2014, at 19:00 UTC.
> Please reply to this email with any proposed agenda items.

I would like the council to approve a preliminary list of features
for EAPI 6, so that the PMS team then can start to work on the
specification.

Of course, the finished PMS spec for EAPI 6 will be brought before the
council again, for final approval.

Here is the list of candidate features, taken from the Wiki page [1]:

1. New features

   a) get_libdir()
        Bug #463586 [2]
        - Used in econf, but so far not available as separate PM function.

   b) einstalldocs()
        Bug #459692 [3]

   c) Query function for IUSE_EFFECTIVE
        Bug #449862 [4]

   d) PATCHES support in default src_prepare()
        Bug #463692 [5]
        - Needs 4a)

2. Extensions to existing features:

   a) nonfatal die()
        Bug #451938 [6]

   b) Allow empty DOCS variable
        Bug #463736 [7]

   c) Directory support for DOCS
        Bug #481980 [8]

   d) Unpack .txz
        Bug #458102 [9]

   e) Case-fold extensions in unpack()
        Bug #476730 [10]

   f) unpack() accept absolute paths
        Bug #483244 [11]

3. Other changes

   a) Bash 4.2
        Bug #431340 [12]

   b) failglob in global scope
        Bug #463822 [13]

4. Features rejected from EAPI 5

   a) Patch applying function in package manager
        Bug #463768 [14]
        - Needed for 2d) and 4b)
        - This will duplicate epatch() from eutils, in simplified form.
        - Name "eapply" has been suggested.

   b) User patches
        Bug #475288 [15], PMS wording [16]
        - Needs 4a)
        - Current wording of the spec requires that every ebuild must
          include a call to the function in src_prepare, which is
          controversial.
        - Names "apply_user_patches" or "eapply_user" have been suggested.

   c) EJOBS variable
        Bug #273101 [17], gentoo-dev discussion [18]
        - Discussion was in 2008. Is there (still) consensus?

   d) Source eclasses only once
        Bug #422533 [19], gentoo-dev discussion [20]

   e) HDEPEND: host dependencies for cross-compilation
        Bug #317337 [21]

   f) Directory support for package* and use*
        Bug #282296 [22]
        - Not intended for gentoo-x86 tree, only to be used in
        overlays.

Ulrich


[1] https://wiki.gentoo.org/wiki/Future_EAPI/EAPI_6_tentative_features
[2] https://bugs.gentoo.org/show_bug.cgi?id=463586
[3] https://bugs.gentoo.org/show_bug.cgi?id=459692
[4] https://bugs.gentoo.org/show_bug.cgi?id=449862
[5] https://bugs.gentoo.org/show_bug.cgi?id=463692
[6] https://bugs.gentoo.org/show_bug.cgi?id=451938
[7] https://bugs.gentoo.org/show_bug.cgi?id=463736
[8] https://bugs.gentoo.org/show_bug.cgi?id=481980
[9] https://bugs.gentoo.org/show_bug.cgi?id=458102
[10] https://bugs.gentoo.org/show_bug.cgi?id=476730
[11] https://bugs.gentoo.org/show_bug.cgi?id=483244
[12] https://bugs.gentoo.org/show_bug.cgi?id=431340
[13] https://bugs.gentoo.org/show_bug.cgi?id=463822
[14] https://bugs.gentoo.org/show_bug.cgi?id=463768
[15] https://bugs.gentoo.org/show_bug.cgi?id=475288
[16] http://git.overlays.gentoo.org/gitweb/?p=proj/pms.git;a=commit;h=a8bf7862967cce36b7f1b408934a774126da2538
[17] https://bugs.gentoo.org/show_bug.cgi?id=273101
[18] http://archives.gentoo.org/gentoo-dev/msg_750e33f68b16d971dff1f40dd9145e56.xml
[19] https://bugs.gentoo.org/show_bug.cgi?id=422533
[20] http://marc.info/?l=gentoo-dev&m=134493783816587&w=2
[21] https://bugs.gentoo.org/show_bug.cgi?id=317337
[22] https://bugs.gentoo.org/show_bug.cgi?id=282296

[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]

       reply	other threads:[~2014-05-29 13:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAGfcS_nydQyxTBw1h0J37o2k7hTRDCdEyy=z=f02geLtauy++Q@mail.gmail.com>
2014-05-29 13:56 ` Ulrich Mueller [this message]
2014-05-29 19:03 ` [gentoo-project] Re: [gentoo-dev-announce] Call For Agenda Items - 10 Jun 2014 Andreas K. Huettel
2014-05-29 21:45   ` [gentoo-project] Maximum number of EAPIs in tree (was: Call For Agenda Items - 10 Jun 2014) Ulrich Mueller
2014-05-29 23:27     ` Rich Freeman
2014-05-30  0:11       ` Jeroen Roovers
2014-05-30  1:31         ` Rich Freeman
2014-05-30  1:33       ` Ulrich Mueller
2014-06-05 16:06   ` [gentoo-project] Re: [gentoo-dev-announce] Call For Agenda Items - 10 Jun 2014 Richard Yao
2014-06-05 16:42     ` Brian Dolbec
2014-06-05 16:55       ` Rich Freeman
2014-06-05 16:56     ` Tom Wijsman
2014-06-03 22:02 ` Andreas K. Huettel
2014-06-07 17:35   ` Roy Bamford
2014-06-07 20:05     ` Rich Freeman
     [not found] ` <CAGfcS_nkawNaJ58cFh1bezQOWe_kNczDfkBC=J0+zEu2chMg4Q@mail.gmail.com>
2014-06-05  6:10   ` [gentoo-project] [gentoo-dev-announce] " Ulrich Mueller

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=21383.15473.683811.968431@a1i15.kph.uni-mainz.de \
    --to=ulm@gentoo.org \
    --cc=gentoo-project@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