| 1 |
В Втр, 25/01/2011 в 14:33 +0100, Thomas Sachau пишет: |
| 2 |
> Do you have some more arguments for your request? Most new developers |
| 3 |
> will have to know about all EAPi versions anyway since they join an |
| 4 |
> existing team with existing ebuilds, which will mostly not use the |
| 5 |
> newest EAPI. |
| 6 |
> |
| 7 |
> As an argument againt this: Noone forces you to keep older EAPI |
| 8 |
> versions of the ebuilds you maintain, you can always bump them to the |
| 9 |
> latest EAPI. But why do you want to force this on all developers? |
| 10 |
|
| 11 |
I think your first paragraph is actually the argument to use latest EAPI |
| 12 |
whenever possible. Such policy provides us with the path to avoid |
| 13 |
situation you described while insisting on keeping old EAPI's obviously |
| 14 |
will force new developer to learn ancient knowledge. IOW, such policy |
| 15 |
provides path to simplify work in team. |
| 16 |
|
| 17 |
-- |
| 18 |
Peter. |
Archives