On Thu, 24 Sep 2009, Maciej Mrozowski wrote:
Because SCM bootstrap is either not used at all, or used very
rarely, there's suggestion to:
- either drop it
- or (preferably) to make SCM eclasses export src_prepare only on
specific request
- or to make it easier - to not export it at all -
# Rémi Cardona r...@gentoo.org (24 Sep 2009)
# Both require xorg-server's libxf86config library which is busted
# and they both have no maintainer. See bug #222683
# Masked for removal in 30 days
dev-python/pyxf86config
dev-python/rhpxl
Cheers,
Rémi
On Thursday 24 of September 2009 08:32:53 Ulrich Mueller wrote:
It's all about making live - tagged ebuild synchronization easier.
Currently
Not a good idea, IMHO. In pre-EAPI-2, the SCM eclasses shadow
src_unpack of base.eclass, so also no autopatching of base.eclass
takes place. If we now
On Thu, 24 Sep 2009 03:39:26 +0200
Maciej Mrozowski reave...@poczta.fm wrote:
And this is the problem (some people may be even unaware of it).
In pre EAPI-2 it was sufficient to do the following in live ebuilds:
inherit ${some_eclass} ${scm_eclass}
${scm_eclass} inherited as last one,
