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: "Paweł Hajdan, Jr." <phajdan.jr@g.o>
Subject: Re: RFC: per package eclass GLEP
Date: Tue, 21 Sep 2010 11:57:37 +0200
On 9/20/10 7:30 PM, Alec Warner wrote:
> How does it provide more code sharing than the existing system?
> 
> Previously I could put code I wanted shared:
> 1) In a global eclass, which means any ebuild in the tree can likely use it

A global eclass is quite heavyweight. It requires a review on
gentoo-dev, is difficult to deprecate, and so on. That's discouraging if
you only want to share 2-3 simple functions used by only one package.

> 2) In a pkg eblit

Which is hacky.

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

No. It lowers the barrier to entry in cases where the shared code is
only useful for one package. It can always be promoted to a global
eclass later (with a proven API).

Paweł

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:
omitting redirecting man pages from compression
Previous by date:
Re: omitting redirecting man pages from compression
Next by date:
Re: omitting redirecting man pages from compression


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.