1 |
On Fri, Mar 16, 2018 at 12:00:47PM +0100, Ulrich Mueller wrote: |
2 |
> >>>>> On Fri, 16 Mar 2018, Martin Vaeth wrote: |
3 |
> |
4 |
> > Ulrich Mueller <ulm@g.o> wrote: |
5 |
> >> |
6 |
> >> I think the conclusion is that github generates tarballs on the |
7 |
> >> fly, and therefore we cannot rely on them being invariant over a |
8 |
> >> long time. |
9 |
> |
10 |
> > So I would not worry too much about it: It is not worth the cost of |
11 |
> > hosting a huge number of tarballs permanently |
12 |
> |
13 |
> I agree, because hosting tarballs of upstream packages is not a task |
14 |
> for us as a distro. |
15 |
> |
16 |
> > (or to convince upstream to let them be hosted by github for every |
17 |
> > single version, only because one cannot theoretically exclude that a |
18 |
> > similar thing won't ever happen again). [...] |
19 |
> |
20 |
> In the first place, upstream should make proper releases, which |
21 |
> includes creating a pristine tarball and permanently hosting it. |
22 |
> So, yell at them if they don't. And no, a git tag is not a release. |
23 |
> |
24 |
> Ulrich |
25 |
|
26 |
Yelling at an upstream might get you somewhere, but you can't force |
27 |
them, and in this case, they might tell you to create the pristine |
28 |
tarball yourself using "git archive" if you want one. |
29 |
|
30 |
I am in the same camp as Martin and James. I would rather see the issues |
31 |
fixed for the specific packages involved than us try to host tarballs |
32 |
for every package that doesn't create them. |
33 |
|
34 |
William |