On 27 September 2013 08:02, Martin Vaeth
va...@mathematik.uni-wuerzburg.dewrote:
For those which are provided by perl itself, you could have
a corresponding useflag of dev-lang/perl and make a use dependency:
If the main perl tarball does not provide the package, the perl ebuild
can pull in
Am Donnerstag, 26. September 2013, 20:11:04 schrieb Kent Fredric:
On 27 September 2013 05:57, Ciaran McCreesh
ciaran.mccre...@googlemail.comwrote:
virtual/perl-* is self-inflicted.
How would you recommend it?
How about doing someting eclass-based, similar to add_kdebase_dep, and let
How do we handle packages which install multiple libraries? I'm afraid
forcing such a policy and/or hurrying developers to adapt will only
cause more of poppler-like issues to occur.
Well, the best technical solution for this is probably subslot dictionaries
as suggested in bug 462138. Then,
Dnia 2013-09-26, o godz. 17:24:49
Davide Pesavento p...@gentoo.org napisał(a):
On Thu, Sep 26, 2013 at 4:04 PM, Kent Fredric kentfred...@gmail.com wrote:
On 26 September 2013 19:53, Michał Górny mgo...@gentoo.org wrote:
How do we handle packages which install multiple libraries? I'm
Sorry if this is duplicate: I repost since I cannot see it after
a few hours.
Kent Fredric kentfred...@gmail.com wrote:
On 27 September 2013 08:02, Martin Vaeth
va...@mathematik.uni-wuerzburg.dewrote:
For those which are provided by perl itself, you could have
a corresponding useflag of
On Fri, Sep 27, 2013 at 12:48 PM, Martin Vaeth
va...@mathematik.uni-wuerzburg.de wrote:
I was not suggesting inlining the list into the dependency but
only inlining the USE-flag into the (single) perl ebuild.
Currently if I have a package which needs e.g. Term-ANSI-Color,
but not in a
On 28 September 2013 07:48, Martin Vaeth
va...@mathematik.uni-wuerzburg.dewrote:
Sorry if this is duplicate: I repost since I cannot see it after
a few hours.
Kent Fredric kentfred...@gmail.com wrote:
On 27 September 2013 08:02, Martin Vaeth
va...@mathematik.uni-wuerzburg.dewrote:
Dear Fellows,
I am revisiting this topic based on previous discussions[1,2,3].
There seems to be a constant need for toolchain with a new EAPI. The
only block is how can we upgrade from an ancient system?, don't bump
or the upgrade path will be break. Let's figure out a solid upgrade
path
