Am Mittwoch 20 Januar 2010 schrieb Michael Sterrett:
> You can look at the discussion at
> http://bugs.gentoo.org/show_bug.cgi?id=288905 but with the last
> release in 2003 it seems like a pretty dead package.
As we seem to have nothing else that can open dzip files and they are used in
the wild,
* Torsten Veller :
> Or do we want to provide it via profiles/base/profile.bashrc like elog?
That wouldn't work as other package managers don't source profile.bashrc.
On 01/22/2010 10:58 AM, Torsten Veller wrote:
> EAPI-3 was approved by the council during their last meeting (2010-01-18).
>
> Which portage versions do support it?
> (I wasn't able to find it in the docs.)
>
I haven't heard of a release that would.
> When can we stabilize EAPI-3 ebuilds?
> (I
A number of ebuilds use vecho from portage.
But vecho is not defined in general. It's a portage internal command.
Do we want to fix the ebuilds? Add a repoman check so we don't have to clean
them regularly?
Or do we want to provide it via profiles/base/profile.bashrc like elog?
BTW: Do we want
EAPI-3 was approved by the council during their last meeting (2010-01-18).
Which portage versions do support it?
(I wasn't able to find it in the docs.)
When can we stabilize EAPI-3 ebuilds?
(I guess this is again a council decision?)
How long do we have to provide ebuilds for older EAPIs?
(We c
