From: "Tomáš Chvátal" <scarabeus@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Fwd: [gentoo-dev-announce] Call for items for September 13 council meeting
Date: Wed, 7 Sep 2011 16:27:01 +0200 [thread overview]
Message-ID: <CA+NrkpdDgkm4NGNcB+2PcHAAGHUp9AcCChVcij2u1BXcZVdq9w@mail.gmail.com> (raw)
In-Reply-To: <20071.28643.758959.906951@a1i15.kph.uni-mainz.de>
2011/9/7 Ulrich Mueller <ulm@gentoo.org>:
>>>>>> On Wed, 7 Sep 2011, Tomáš Chvátal wrote:
>
>> Start collecting ideas for EAPI5.
>
> I suggest that EAPI 5 should include the two features that have been
> omitted from EAPI 4 [1,2].
>
> Apart from this, I think we should be more careful for the next EAPI,
> in order to avoid such long delays as we had with EAPI 4. One possible
> solution would be to only accept features where a preliminary
> implementation in Portage is available.
Agreed the wait last time was really bad.
>
>> I myself would like PATCHES array to be default in src_prepare phase
>> and some solution for runtime optional deps, Instead of elog in
>> postinst something like Recommended from rpm.
>
> Looks reasonable (if an implementation is ready). Although I don't
> understand how it is related to rpm.
Well the patches code is in base eclass.
For Recommended it works like this:
blabla.spec
Recommended: xf86-video-ati
zypper in blabla
...
You might consider installing these additional packages:
xf86-video-ati
It for sure needs more thinking as this is just basic idea. It might
even take into account that if you install the recommended patckage
with oneshot it should not be depcleaned unless all recommending
packages are gone too, and so on.
next prev parent reply other threads:[~2011-09-07 14:29 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4E64C7BB.907@gentoo.org>
[not found] ` <CA+Nrkpd499zUJiHee2f9wfoCgRiQCO0EXetowbPdWYmMGoaFkA@mail.gmail.com>
2011-09-07 9:07 ` [gentoo-dev] Fwd: [gentoo-dev-announce] Call for items for September 13 council meeting Tomáš Chvátal
2011-09-07 9:17 ` Andreas K. Hüttel
2011-09-07 13:21 ` Ulrich Mueller
2011-09-07 14:27 ` Tomáš Chvátal [this message]
2011-09-07 15:43 ` Michał Górny
2011-09-07 15:48 ` Michał Górny
2011-09-07 22:47 ` Aaron W. Swenson
2011-09-07 22:53 ` Ciaran McCreesh
2011-09-07 23:04 ` Brian Harring
2011-09-15 7:35 ` Michał Górny
2011-09-15 7:55 ` Ciaran McCreesh
2011-09-15 8:01 ` Michał Górny
2011-09-15 8:07 ` Ciaran McCreesh
2011-09-15 23:21 ` Arfrever Frehtes Taifersar Arahesis
2011-09-15 23:54 ` Brian Harring
2011-09-16 0:20 ` Arfrever Frehtes Taifersar Arahesis
2011-09-16 21:06 ` Zac Medico
2011-09-18 3:47 ` Donnie Berkholz
2011-09-18 5:26 ` Zac Medico
2011-09-18 6:01 ` Brian Harring
2011-09-18 6:57 ` Ulrich Mueller
2011-09-18 9:24 ` Nirbheek Chauhan
2011-09-18 9:33 ` Ciaran McCreesh
2011-09-18 14:20 ` Jorge Manuel B. S. Vicetto
2011-09-18 15:58 ` Ciaran McCreesh
2011-09-18 16:14 ` Rich Freeman
2011-09-18 17:10 ` Nirbheek Chauhan
2011-09-18 17:34 ` Zac Medico
2011-09-18 14:47 ` Michał Górny
2011-09-18 15:54 ` Ciaran McCreesh
2011-09-15 16:51 ` Brian Harring
2011-09-07 16:19 ` Ciaran McCreesh
2011-09-08 17:03 ` Thomas Sachau
2011-09-08 17:41 ` Alec Warner
2011-09-08 17:55 ` Ole Markus With
2011-09-08 18:10 ` Arfrever Frehtes Taifersar Arahesis
2011-09-08 18:35 ` Michał Górny
2011-09-08 18:33 ` Ciaran McCreesh
2011-09-08 18:43 ` Michał Górny
2011-09-09 0:45 ` Mike Frysinger
2011-09-18 11:08 ` proposal for cross-compie support in EAPI-5, was: " Thomas Sachau
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=CA+NrkpdDgkm4NGNcB+2PcHAAGHUp9AcCChVcij2u1BXcZVdq9w@mail.gmail.com \
--to=scarabeus@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