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