| 1 |
W dniu śro, 21.02.2018 o godzinie 00∶32 +0100, użytkownik Ulrich Mueller |
| 2 |
napisał: |
| 3 |
> > > > > > On Tue, 20 Feb 2018, Michał Górny wrote: |
| 4 |
> |
| 5 |
> |
| 6 |
> > +- zero or more ``<stabilize-allarches/>`` elements, possibly restricted |
| 7 |
> > + to specific package versions (at most one for each version) whose presence |
| 8 |
> |
| 9 |
> Rather than versions, it might make more sense to allow restricting |
| 10 |
> this to specific slots. I suggest to update the "restrict" attribute |
| 11 |
> to EAPI 5 dependency specifications (either for this element only, |
| 12 |
> or globally). |
| 13 |
> |
| 14 |
|
| 15 |
Not sure if that's a good idea. Not that anything I know really parses |
| 16 |
restrict="" but (unlike adding a new element) changing the semantics of |
| 17 |
it is not backwards-compatible. |
| 18 |
|
| 19 |
Also, should we allow USE-dependencies in it then? How should they be |
| 20 |
evaluated? |
| 21 |
|
| 22 |
-- |
| 23 |
Best regards, |
| 24 |
Michał Górny |
Archives