| 1 |
Am Samstag, 27. September 2014, 15:08:57 schrieb Michał Górny: |
| 2 |
> Dnia 2014-09-23, o godz. 16:52:56 |
| 3 |
> |
| 4 |
> "Andreas K. Huettel" <dilfridge@g.o> napisał(a): |
| 5 |
> > > > Modified: ChangeLog perl-module.eclass |
| 6 |
> > > > Log: |
| 7 |
> > > > Remove support for EAPI 1, 2, 3 in perl-module.eclass (no packages |
| 8 |
> > > > left in the tree) |
| 9 |
> > > |
| 10 |
> > > This could have used some kind of heads-up. Now I'm getting a lot of |
| 11 |
> > > metadata generation errors due to overlays still using those EAPIs. |
| 12 |
> > |
| 13 |
> > True, this could have been done in more elegant ways, i.e. first an ugly |
| 14 |
> > deprecation warning for some time. (Usually we don't care too much about |
| 15 |
> > overlays. Here, it's g-cpan that concerns me.) |
| 16 |
> > |
| 17 |
> > Would it still make sense to do that? |
| 18 |
> > (i.e. re-allow 123 for a while and add a warning?) |
| 19 |
> |
| 20 |
> Yes, that would reduce the amount of breakage e.g. due to sunrise |
| 21 |
> ebuilds using that. Not that I expect people to actually fix the |
| 22 |
> ebuilds but I'd have a little less chatter during cache regen :). |
| 23 |
|
| 24 |
OK now there's just a big fat ewarn that support will be removed on 1/Nov. |
| 25 |
|
| 26 |
Gives everyone a month time to fix the ebuilds; then we can remove support and |
| 27 |
clean up the eclass. |
| 28 |
|
| 29 |
-- |
| 30 |
|
| 31 |
Andreas K. Huettel |
| 32 |
Gentoo Linux developer |
| 33 |
dilfridge@g.o |
| 34 |
http://www.akhuettel.de/ |
Archives