On Thu, 2008-02-14 at 16:03 +0200, Petteri Räty wrote:
> Peter Volkov kirjoitti:
> >
> > May be we should punt them from the tree?
> >
>
> Eclasses can't be removed...
Well, this isn't really true anymore thanks to bug #46223 being
resolved. I'd say that it only makes sense that we keep them a
On Thu, 2008-02-14 at 16:52 +0300, Peter Volkov wrote:
> The check was done with the following script:
>
> find /usr/portage \( -name '*.ebuild' -o -name '*.eclass' \) \
> -exec awk "/inherit.*[[:blank:]]+${eclass}([[:blank:]]+.*|$+)/{print FILENAME
> }" \{\} \;
>
> For inherit eclass I've searc
On Thu, 14 Feb 2008 16:52:57 +0300
Peter Volkov <[EMAIL PROTECTED]> wrote:
> May be we should punt them from the tree?
Can't until everyone's using a package manager with working env saving.
> inherit - I did not found ebuilds where it is used, but actually I do
> not know how it was used, so may
Petteri Räty a écrit :
Peter Volkov kirjoitti:
May be we should punt them from the tree?
Eclasses can't be removed...
Arguably we could specify a time period before they can be removed? This
is probably GLEP material though :)
Maybe we should have a deprecated eclass for showing a commo
Peter Volkov kirjoitti:
May be we should punt them from the tree?
Eclasses can't be removed...
Maybe we should have a deprecated eclass for showing a common messaged
that certain eclasses should not be used. Then deprecated eclasses could
be detected by looking if they inherit deprecated.
В Чтв, 14/02/2008 в 02:10 +0200, Mart Raudsepp пишет:
> On K, 2008-02-13 at 15:49 -0500, Doug Klima wrote:
> >
> > deprecated eclasses:64-bit, darcs, db4-fix, debian, embassy-2.10,
> > embassy-2.9, gcc, gnustep-old, gtk-engines, gtk-engines2, inherit,
> > jakarta-commons, java-pkg, jav
