1 |
On Sun, Jun 27, 2010 at 1:29 AM, Ciaran McCreesh |
2 |
<ciaran.mccreesh@××××××××××.com> wrote: |
3 |
> On Sat, 26 Jun 2010 21:46:39 +0200 |
4 |
> Enrico Weigelt <weigelt@×××××.de> wrote: |
5 |
>> BTW: if upstream has an proper VCS and an canonical tagging |
6 |
>> scheme, they don't actually have to create release tarballs, |
7 |
>> just hack up a little script which creates them on-the-fly |
8 |
>> from an canonical URL scheme (eg. oss-qm does exactly that). |
9 |
> |
10 |
> Down that path lies madness. There's no guarantee that you'll get the |
11 |
> same tarball if you request the same URL twice in a row, particularly |
12 |
> if you're using one of those new-fangled new compression schemes. |
13 |
> |
14 |
|
15 |
Or if they generate the tarball on-the-fly with no caching, which |
16 |
results in differing timestamps each time. Hence, each time you fetch |
17 |
it, you get a tarball with a different hash. |
18 |
|
19 |
No, don't ask where I saw such a thing :p |
20 |
|
21 |
-- |
22 |
~Nirbheek Chauhan |
23 |
|
24 |
Gentoo GNOME+Mozilla Team |