1 |
On Wed, Jan 17, 2018 at 10:25 AM, Michał Górny <mgorny@g.o> wrote: |
2 |
|
3 |
> W dniu wto, 16.01.2018 o godzinie 11∶32 -0800, użytkownik Zac Medico |
4 |
> napisał: |
5 |
> > On 01/16/2018 10:39 AM, Michał Górny wrote: |
6 |
> > > W dniu wto, 16.01.2018 o godzinie 12∶44 -0500, użytkownik Alec Warner |
7 |
> > > napisał: |
8 |
> > > > On Tue, Jan 16, 2018 at 11:43 AM, Michał Górny <mgorny@g.o> |
9 |
> wrote: |
10 |
> > > > |
11 |
> > > > > Include a repo.postsync.d hook to verify the rsync checkout using |
12 |
> > > > > gemato. Given that not all people will want to have it enabled |
13 |
> > > > > unconditionally, no setup.py rules are included -- instead, the |
14 |
> file |
15 |
> > > > > would be installed conditionally by the ebuild. |
16 |
> > > > > |
17 |
> > > > > [v2: included link to the wiki page] |
18 |
> > > > > --- |
19 |
> > > > > MANIFEST.in | 2 +- |
20 |
> > > > > misc/repo.postsync.d/00gemato | 18 ++++++++++++++++++ |
21 |
> > > > > 2 files changed, 19 insertions(+), 1 deletion(-) |
22 |
> > > > > create mode 100644 misc/repo.postsync.d/00gemato |
23 |
> > > > > |
24 |
> > > > > diff --git a/MANIFEST.in b/MANIFEST.in |
25 |
> > > > > index 4f6cac162..edc6704e7 100644 |
26 |
> > > > > --- a/MANIFEST.in |
27 |
> > > > > +++ b/MANIFEST.in |
28 |
> > > > > @@ -14,4 +14,4 @@ include cnf/make.conf.example.* |
29 |
> > > > > include .portage_not_installed |
30 |
> > > > > |
31 |
> > > > > # extra scripts |
32 |
> > > > > -include misc/* |
33 |
> > > > > +graft misc |
34 |
> > > > > diff --git a/misc/repo.postsync.d/00gemato b/misc/repo.postsync.d/ |
35 |
> 00gemato |
36 |
> > > > > new file mode 100644 |
37 |
> > > > > index 000000000..f2af50925 |
38 |
> > > > > --- /dev/null |
39 |
> > > > > +++ b/misc/repo.postsync.d/00gemato |
40 |
> > > > > @@ -0,0 +1,18 @@ |
41 |
> > > > > +#!/bin/bash |
42 |
> > > > > +# repo.postsync.d hook to verify ::gentoo checkout using gemato |
43 |
> > > > > + |
44 |
> > > > > +name=${1} |
45 |
> > > > > +url=${2} |
46 |
> > > > > +path=${3} |
47 |
> > > > > + |
48 |
> > > > > +# keyring installed by gentoo-keys |
49 |
> > > > > +openpgp_key=/var/lib/gentoo/gkeys/keyrings/gentoo/release/ |
50 |
> pubring.gpg |
51 |
> > > > > |
52 |
> > > > |
53 |
> > > > This seems a bit leaky to me. |
54 |
> > > > |
55 |
> > > > Possible to get gentoo-keys to print it? |
56 |
> > > > |
57 |
> > > > e.g: |
58 |
> > > > |
59 |
> > > > openpgp_key=$(gentoo-keys --print-key-path) |
60 |
> > > |
61 |
> > > But app-crypt/gentoo-keys doesn't include that executable, and it has |
62 |
> > > no dependency on app-crypt/gkeys. I'd rather not introduce an |
63 |
> artificial |
64 |
> > > dependency here. |
65 |
> > |
66 |
> > I suppose we could using a separate ebuild to install this hook, so that |
67 |
> > we can update it separately from portage if necessary. The hook can |
68 |
> > still live in the portage repository (like emerge-delta-webrsync which |
69 |
> > is also installed by a separate ebuild). |
70 |
> |
71 |
> I don't see a strong reason to add yet another rebuild for a single file |
72 |
> that is going to be updated really rarely. However, if we're going to do |
73 |
> it that way, then there's no point in putting it in Portage repository. |
74 |
> |
75 |
> However, this 'update it separately from portage' reminds me of repoman |
76 |
> that frequently gets seriously outdated and/or incompatible with Portage |
77 |
> because of independent release cycle... |
78 |
> |
79 |
|
80 |
I'll rephrase my objection. |
81 |
|
82 |
I don't care what you do as long as Zac (the person releasing portage) |
83 |
agrees with whatever |
84 |
requirements you need. If we need 3 releases in a row because the hook is |
85 |
buggy, as long as |
86 |
Zac is happy with that I'm happy with that. |
87 |
|
88 |
What I don't want to see is surprise when the hook is cut and suddenly its |
89 |
buggy and we need new |
90 |
cuts and Zac is not around, or HEAD is broken, or some other problem. |
91 |
|
92 |
Looking at the release history, multiple cuts in O(few) days is fairly |
93 |
common (11/20, 11/21, 12/10, 12/15) |
94 |
so this seems low risk to me; but AFAIK Zac is usually driving these |
95 |
changes himself so its a bit more obvious |
96 |
what is going on. Or just allow Michał to cut his own portage releases when |
97 |
he needs hook updates. |
98 |
|
99 |
-A |
100 |
|
101 |
|
102 |
> |
103 |
> -- |
104 |
> Best regards, |
105 |
> Michał Górny |
106 |
> |
107 |
> |
108 |
> |