1 |
Dnia 2014-03-03, o godz. 15:05:12 |
2 |
Ian Stakenvicius <axs@g.o> napisał(a): |
3 |
|
4 |
> -----BEGIN PGP SIGNED MESSAGE----- |
5 |
> Hash: SHA256 |
6 |
> |
7 |
> On 03/03/14 02:43 PM, Michał Górny wrote: |
8 |
> > Dnia 2014-03-03, o godz. 12:14:13 Ulrich Mueller <ulm@g.o> |
9 |
> > napisał(a): |
10 |
> > |
11 |
> >>>>>>> On Thu, 27 Feb 2014, Anthony G Basile wrote: |
12 |
> >> |
13 |
> >>> I'm putting the call out there for any agenda items for the |
14 |
> >>> next Council meeting, which will be held on March 11, 2014 at |
15 |
> >>> 1900 UTC. This is short notice but we got off track because of |
16 |
> >>> FOSDEM and we're going to try to get back on track. |
17 |
> >> |
18 |
> >> In February we have voted to "ban new EAPI 1 and 2 ebuilds". Now |
19 |
> >> I've seen some commits where ebuilds were changed in place from |
20 |
> >> EAPI 0 to EAPI 1. |
21 |
> >> |
22 |
> >> Can we clarify that the ban includes updating the EAPI in |
23 |
> >> existing ebuilds? |
24 |
> > |
25 |
> > So how we are supposed to handle updating rev-deps to use proper |
26 |
> > slot? Convert ancient versions to a new EAPI or just drop them |
27 |
> > completely? |
28 |
> > |
29 |
> |
30 |
> That's up to you, as maintainer, isn't it? |
31 |
|
32 |
If I am fixing a few dozen ebuilds due to change in dependency package, |
33 |
I'm not the maintainer. |
34 |
|
35 |
-- |
36 |
Best regards, |
37 |
Michał Górny |