| 1 |
On Fri, Jan 26, 2018 at 7:48 PM, Michael Orlitzky <mjo@g.o> wrote: |
| 2 |
> On 01/26/2018 06:24 PM, Michał Górny wrote: |
| 3 |
>> |
| 4 |
>> The alternate option of using file hash has the advantage of having |
| 5 |
>> a more balanced split. Furthermore, since hashes are stored |
| 6 |
>> in Manifests using them is zero-cost. However, this solution has two |
| 7 |
>> significant disadvantages: |
| 8 |
>> |
| 9 |
>> 1. The hash values are unknown for newly-downloaded distfiles, so |
| 10 |
>> ``repoman`` (or an equivalent tool) would have to use a temporary |
| 11 |
>> directory before locating the file in appropriate subdirectory. |
| 12 |
>> |
| 13 |
>> 2. User-provided distfiles (e.g. for fetch-restricted packages) with |
| 14 |
>> hash mismatches would be placed in the wrong subdirectory, |
| 15 |
>> potentially causing confusing errors. |
| 16 |
>> |
| 17 |
> |
| 18 |
> The filename proposal sounds fine, |
| 19 |
|
| 20 |
I've had to interact with the distfile server by hand, and would |
| 21 |
appreciate it if the files can be maintained in some way that finding |
| 22 |
them is obvious without tools. |
| 23 |
|
| 24 |
Every once and a while I navigate to the distfile root and need to |
| 25 |
forcefully exit Firefox. |
| 26 |
|
| 27 |
Cheers, |
| 28 |
R0b0t1 |
Archives