1 |
El dom, 18-12-2011 a las 23:02 +0100, Michał Górny escribió: |
2 |
[...] |
3 |
> > Q6: Why can't the dodoc/dohtml path be changed before EAPI-5? |
4 |
> > A6: Because the path where dodoc and dohtml install files is part of |
5 |
> > the PMS. Portage can't just change it on its own. A possible |
6 |
> > workaround for current EAPIs is adding new-style dodoc/dohtml |
7 |
> > analogues to an eclass. |
8 |
> |
9 |
> I think some of devs agree we should be allowed to fix past mistakes |
10 |
> without waiting another 20 years till the tree is migrated to a new |
11 |
> EAPI... |
12 |
> |
13 |
|
14 |
Maybe this situation could be improved if there was a policy forcing us |
15 |
to try to use latest EAPI when possible for any package update, that way |
16 |
we would move faster to latest eapi and even deprecate older eapis |
17 |
easily |