| 1 |
On Tue, Sep 23, 2014 at 04:52:56PM +0200, Andreas K. Huettel wrote: |
| 2 |
> |
| 3 |
> > > Modified: ChangeLog perl-module.eclass |
| 4 |
> > > Log: |
| 5 |
> > > Remove support for EAPI 1, 2, 3 in perl-module.eclass (no packages left |
| 6 |
> > > in the tree) |
| 7 |
> > This could have used some kind of heads-up. Now I'm getting a lot of |
| 8 |
> > metadata generation errors due to overlays still using those EAPIs. |
| 9 |
> |
| 10 |
> True, this could have been done in more elegant ways, i.e. first an ugly |
| 11 |
> deprecation warning for some time. (Usually we don't care too much about |
| 12 |
> overlays. Here, it's g-cpan that concerns me.) |
| 13 |
> |
| 14 |
> Would it still make sense to do that? |
| 15 |
> (i.e. re-allow 123 for a while and add a warning?) |
| 16 |
|
| 17 |
I wouldn't bother with it, because I don't think you will find a |
| 18 |
reasonable time that all overlay maintainers will be happy with. |
| 19 |
|
| 20 |
William |
| 21 |
|
| 22 |
tree. |
| 23 |
|
| 24 |
William |
Archives