Gentoo Archives: gentoo-project

From: "Michał Górny" <mgorny@g.o>
To: gentoo-project@l.g.o
Subject: Re: [gentoo-dev] arches.desc & GLEP 72 (was: Re: [gentoo-project] Items for Council Agenda, May 14)
Date: Sat, 13 May 2017 07:44:44
Message-Id: 1494661469.1789.5.camel@gentoo.org
In Reply to: Re: [gentoo-dev] arches.desc & GLEP 72 (was: Re: [gentoo-project] Items for Council Agenda, May 14) by "Andreas K. Huettel"
1 On sob, 2017-05-13 at 02:03 +0200, Andreas K. Huettel wrote:
2 > Lots of improvements implemented, see
3 > https://wiki.gentoo.org/wiki/User:Dilfridge/GLEP:72
4 >
5 > and the notes below for what was done...
6 >
7 >
8 > Am Samstag, 6. Mai 2017, 18:35:08 CEST schrieb Michał Górny:
9 > > 1. I think your example is a bit misleading -- unless I'm missing
10 > > something, mips would be 'unstable' right now, and m68k would be
11 > > 'testing'.
12 >
13 > Fixed.
14 >
15 > > 2. I can't say I like using magical keywords like 'testing'
16 > > and 'unstable'; they're going to be confusing long-term
17 > > I should point out that those terms are frequently used interchangeably,
18 > > and adding disjoint meanings to them is least misleading. Perhaps a name
19 > > like 'transitional' for the middle state would be better?
20 >
21 > I replaced "testing" with "mixed". So now the three values are "stable",
22 > "mixed", "unstable". I think that should be more clear.
23 >
24 > > 3. What is the use case for 'broken'? Are we ever going to use that?
25 >
26 > I don't really know of any, so I've removed this again.
27 >
28 > > Rationale is 'why did I
29 > > choose this specific solution?' -- e.g. choice of file format, keywords
30 > > and basically answers to every useful question that has been raised.
31 >
32 > Added, though I'm not sure it's really complete.
33 >
34 > > > a. whether CI should enforce correct depgraph and how,
35 > >
36 > > Well, my approach for this would be that CI should enforce the same things
37 > > as
38 > > Repoman.
39 >
40 > Changed the wording such that it's not repoman-specific anymore.
41 >
42 >
43 > > > b. whether we should request stabilizing packages.
44 > >
45 > > We could, however, add one more column *only* for the (testing) mixed case,
46 > > which states whether stabilization requests are required.
47 >
48 > Implemented this, now we have a third column. That makes the specs a bit more
49 > complex, but it's probably worth it. And the third column will nearly always
50 > be empty.
51
52 Looks mostly good. Aside to some typos:
53
54 a. 'Meaning of the second column values for other tools' says that
55 stabilization requests on bugzilla are based on second column; I think
56 you should update this to account for the third column.
57
58 b. Do we need a fourth column for keyword requests? I guess not since if
59 we stop supporting specific ~arch, we can probably remove it completely.
60 Which brings the next question....
61
62 c. What should be the behavior for arches that are not listed
63 in arches.desc when the file is present?
64
65 --
66 Best regards,
67 Michał Górny

Attachments

File name MIME type
signature.asc application/pgp-signature

Replies