| 1 |
Ciaran McCreesh a écrit : |
| 2 |
> Kills the upgrade path completely. No good. |
| 3 |
|
| 4 |
Lemme sum this up in layman's terms : |
| 5 |
|
| 6 |
1) EAPI _has_ to be known before sourcing an ebuild. There's no way to |
| 7 |
avoid that for various reasons, all 100% valid. |
| 8 |
|
| 9 |
2) Putting the EAPI in the filename : |
| 10 |
|
| 11 |
+ it solves 1) |
| 12 |
+ it keeps backward compatibility because old PM won't recognize the |
| 13 |
filenames |
| 14 |
- it's not very "pretty" |
| 15 |
|
| 16 |
3) Putting the EAPI in metadata.xml or in another external file |
| 17 |
|
| 18 |
+ it solves 1) |
| 19 |
+ it keeps pretty file names |
| 20 |
- it breaks backwards compatibility |
| 21 |
- (specific to metadata.xml) PM will have to learn to read XML (yuck) |
| 22 |
|
| 23 |
That's about it, right? |
| 24 |
|
| 25 |
|
| 26 |
-- |
| 27 |
Rémi Cardona |
| 28 |
LRI, INRIA |
| 29 |
remi.cardona@×××.fr |
| 30 |
remi@g.o |
| 31 |
-- |
| 32 |
gentoo-dev@l.g.o mailing list |
Archives