1 |
On Thu, 29 Oct 2015 17:13:29 +0100 |
2 |
Chí-Thanh Christopher Nguyễn <chithanh@g.o> wrote: |
3 |
> Ciaran McCreesh schrieb: |
4 |
> > On Thu, 29 Oct 2015 16:22:40 +0100 |
5 |
> > Chí-Thanh Christopher Nguyễn <chithanh@g.o> wrote: |
6 |
> >> The previous time I wanted to post a news item with USE |
7 |
> >> dependencies, this was not possible because the |
8 |
> >> Display-If-Installed dependency atom had to conform to EAPI 0. But |
9 |
> >> now that all profiles are EAPI 5 this is ok I hope. |
10 |
> > It's not really clear what the EAPI for the news directory is... |
11 |
> |
12 |
> I guess you are right, but as all package managers must now |
13 |
> understand EAPI 5 dependency atoms, it is not likely that any will |
14 |
> choke on it. |
15 |
|
16 |
Well Portage won't, since it doesn't do input validation and will |
17 |
pretty much allow you to use any EAPI's syntax anywhere. Paludis will |
18 |
probably warn that you're using an EAPI 5 feature somewhere where EAPI |
19 |
5 hasn't been declared, since everything that isn't explicitly a |
20 |
particular EAPI is EAPI 0. |
21 |
|
22 |
> Besides, existing news items already use |
23 |
> Display-If-Profile: to point to EAPI 5 profiles. |
24 |
|
25 |
That isn't how EAPIs work, conceptually. Whenever a PM does something |
26 |
with a spec, it asks what the EAPI is in the context of that spec, |
27 |
which in turn depends upon where that spec came from. A user using a |
28 |
profile with EAPI 5 does not mean that every dep spec is treated as |
29 |
being EAPI 5 -- the profile EAPI just applies to things from that |
30 |
particular profiles directory. (And even if it did work the way you |
31 |
think, users not using an EAPI 5 profile would still need to be able to |
32 |
parse that news item...) |
33 |
|
34 |
> But I can ask the Council for clarification on the issue. |
35 |
|
36 |
Not so much a Council issue as a PMS one, but the trouble is that news |
37 |
items slightly predate PMS and EAPIs. |
38 |
|
39 |
-- |
40 |
Ciaran McCreesh |