>>>>> On Sun, 31 Aug 2014, Ulrich Mueller wrote: >>>>> On Sat, 30 Aug 2014, Michał Górny wrote: >> As I see it, we should simply ban einstall in EAPI 6. This way, we >> can prevent further mistakes from happening and let developers fix >> the current consumers once bumping EAPI (or lastrite them at some >> point).
> It may be worth mentioning that econf in EAPI 6 will pass --docdir
> and --htmldir options to configure. These would take precedence over
> einstall's prefix="${ED}"/usr, i.e. einstall's path for documentation
> files would be broken because ${D} would be missing from it.
> So _if_ we decide to keep einstall, then we would have to pass
> additional docdir and htmldir variables. OTOH, maybe this would be a
> good occasion for getting rid of the function.
I see no further replies to this thread, so I will raise this as an
item for the next council meeting.
Currently, only 218 ebuilds are using einstall, which is less than
0.6 % of all ebuilds in the tree.
Ulrich
pgpXjI6uMObkK.pgp
Description: PGP signature
