Re: [gentoo-dev] Collecting items for EAPI 6
On Sat, 30 Mar 2013 12:39:14 -0600 Christoph Junghans wrote: > 2013/3/28 Michał Górny : > > 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 > > > #444366 - unique subslot for live ebuilds Has anyone tried implementing this and using it in practice? -- Ciaran McCreesh signature.asc Description: PGP signature
Re: [gentoo-dev] Collecting items for EAPI 6
2013/3/28 Michał Górny : > 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 > #444366 - unique subslot for live ebuilds -- Christoph Junghans http://dev.gentoo.org/~ottxor/
Re: [gentoo-dev] Collecting items for EAPI 6
Am Freitag, 29. März 2013, 17:57:34 schrieb Ciaran McCreesh: [snip] > /dev/null -- Andreas K. Huettel Gentoo Linux developer dilfri...@gentoo.org http://www.akhuettel.de/
Re: [gentoo-dev] Collecting items for EAPI 6
On Fri, 29 Mar 2013 18:54:52 +0100 "Andreas K. Huettel" wrote: > Am Donnerstag, 28. März 2013, 19:15:59 schrieb Michał Górny: > > 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 > > > > IUSE_RUNTIME support. Please. > https://bugs.gentoo.org/show_bug.cgi?idB4283 Without a reference implementation, and experience of how it works in practice? No chance. We have both of these for 'suggested' dependencies, if you prefer. -- Ciaran McCreesh signature.asc Description: PGP signature
Re: [gentoo-dev] Collecting items for EAPI 6
Am Donnerstag, 28. März 2013, 19:15:59 schrieb Michał Górny: > 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 > IUSE_RUNTIME support. Please. https://bugs.gentoo.org/show_bug.cgi?idB4283 -- Andreas K. Huettel Gentoo Linux developer dilfri...@gentoo.org http://www.akhuettel.de/ signature.asc Description: This is a digitally signed message part.
Re: [gentoo-dev] Collecting items for EAPI 6
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
Re: [gentoo-dev] Collecting items for EAPI 6
Dne Čt 28. března 2013 19:15:59, Michał Górny napsal(a): > 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 > > As it goes we have lafile removal scripts in eclass already and there seems to be no harm done to users anymore with by-default punting with new eapi. https://bugs.gentoo.org/show_bug.cgi?id57561 Patches array from base eclass to default as it is last thing in base eclass that has some relevant stuff. https://bugs.gentoo.org/show_bug.cgi?idF3692 Other than that I would like to see some improvements on binary packages (no bugs). Something like different binary pkgs for various IUSE (so they are not always rewritten)... so the tinderbox can get more usefull :-) Cheers Tom signature.asc Description: This is a digitally signed message part.
[gentoo-dev] Collecting items for EAPI 6
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). -- Best regards, Michał Górny signature.asc Description: PGP signature
