Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-dev
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-dev@g.o
From: Matti Bickel <mabi@g.o>
Subject: Re: RFC: per package eclass GLEP
Date: Mon, 20 Sep 2010 23:20:47 +0200
On 09/20/2010 07:30 PM, Alec Warner wrote:
> Under the new system I can put the code:
> 
> 1) In a global eclass, any ebuild can likely use it
> 2) In a per-package eclass, only one package can use it
> 3) In a pkg eblit, only one package can use it

Per package eclasses are pretty much eblits with some PM support thrown in.

> Wouldn't taking code from a global eclass and moving it to a
> per-package eclass limit code re-use?

No, code reuse will stay the same. What I like about the idea is moving
more of the code closer to the ebuild files, tightening it's scope. No
more wondering (as an ebuild author) if and how I could use
php5_2-sapi.eclass - it just wouldn't be there.

I'll answer more points tomorrow, but thanks for your ideas!

Attachment:
signature.asc (OpenPGP digital signature)
References:
RFC: per package eclass GLEP
-- Matti Bickel
Re: RFC: per package eclass GLEP
-- PaweĊ‚ Hajdan, Jr.
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: RFC: per package eclass GLEP
Next by thread:
Re: RFC: per package eclass GLEP
Previous by date:
Re: openrc stabilization update
Next by date:
Re: openrc stabilization update


Updated Jun 29, 2012

Summary: Archive of the gentoo-dev mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.