| 1 |
On Wed, Mar 18, 2020 at 9:59 PM Kent Fredric <kentnl@g.o> wrote: |
| 2 |
> |
| 3 |
> On Wed, 18 Mar 2020 17:52:25 +0000 |
| 4 |
> James Le Cuirot <chewi@g.o> wrote: |
| 5 |
> |
| 6 |
> > Not quite. Tools like repoman will need to be updated to understand |
| 7 |
> > that an ebuild with KEYWORDS="amd64" can depend on another ebuild with |
| 8 |
> > only KEYWORDS="noarch". I do think the idea has merit though. |
| 9 |
> |
| 10 |
> But the inverse is _not_ true, an ebuild with KEYWORDS="noarch" |
| 11 |
> *cannot* depend on another ebuild with only KEYWORDS="amd64". |
| 12 |
> |
| 13 |
> Otherwise it breaks the entire stabilization graph. |
| 14 |
|
| 15 |
I'm not sure what you mean by "stabilization graph". I'm guessing you |
| 16 |
mean the dependency graph for stable keywords? |
| 17 |
|
| 18 |
Valid dependency graphs are determined by whatever our tooling deems |
| 19 |
valid. The tooling could be updated to permit amd64 packages to depend |
| 20 |
on noarch packages, and vice-versa. |
Archives