1 |
On Wed, 18 Mar 2020 12:47:53 -0500 |
2 |
William Hubbs <williamh@g.o> wrote: |
3 |
|
4 |
> On Wed, Mar 18, 2020 at 06:12:37PM +0100, Michał Górny wrote: |
5 |
> > On Wed, 2020-03-18 at 09:54 -0500, William Hubbs wrote: |
6 |
> > > this came up again on the recent thread about dropping non x86/amd64 |
7 |
> > > support for python packages, and I want to bring it up again on its own |
8 |
> > > thread. |
9 |
> > > |
10 |
> > > How often do architecture specific bugs really exist in languages like |
11 |
> > > perl, python etc? From what I've seen they are pretty rare. Not to mention, |
12 |
> > > if we found one somewhere, we could adjust keywords as necessary. |
13 |
> > > |
14 |
> > > Also, if someone did inadvertently keyword a package with noarch that didn't |
15 |
> > > work everywhere, it would be a matter of adjusting the keywords for that |
16 |
> > > package. |
17 |
> > > |
18 |
> > > So, my question is, why can't we add a noarch/~noarch keyword and see |
19 |
> > > how things go? If it gets abused we can always nuke it later. |
20 |
> > > |
21 |
> > |
22 |
> > 1. How is this going to work when noarch package depends on non-nonarch |
23 |
> > package? I mean, will all the package managers actually work? Have you |
24 |
> > did some minimal testing before bringing this up? |
25 |
> |
26 |
> Can you have multiple ACCEPT_KEYWORDS values in make.conf or |
27 |
> make.defaults like this? |
28 |
> |
29 |
> ACCEPT_KEYWORDS="amd64 noarch" |
30 |
> |
31 |
> If so, things should just work. |
32 |
|
33 |
Not quite. Tools like repoman will need to be updated to understand |
34 |
that an ebuild with KEYWORDS="amd64" can depend on another ebuild with |
35 |
only KEYWORDS="noarch". I do think the idea has merit though. |
36 |
|
37 |
-- |
38 |
James Le Cuirot (chewi) |
39 |
Gentoo Linux Developer |