1 |
>>>>> On Mon, 13 Sep 2021, Sheng Yu wrote: |
2 |
|
3 |
> -The archive contains a number of files, stored in a single directory |
4 |
> -whose name should match the basename of the package file. However, |
5 |
> -the implementation must be able to process an archive where |
6 |
> -the directory name is mismatched. There should be no explicit archive |
7 |
> -member entry for the directory. |
8 |
> +The archive contains a number of files. All package-related files |
9 |
> +should be stored in a single directory whose name matches the CPV of |
10 |
> +the package file. However, the implementation must be able to process |
11 |
> +an archive where the directory name is mismatched. There should be no |
12 |
> +explicit archive member entry for the directory. |
13 |
|
14 |
I wonder about CPV here. That's ${CATEGORY}/${P} and contains a slash, |
15 |
so it cannot be the name of a directory. Also, what about the package |
16 |
revision? |
17 |
|
18 |
> +6. The package manifest data file ``Manifest`` (required). |
19 |
> + |
20 |
> +7. A signature for the package Manifest file ``Manifest.sig`` |
21 |
> + (optional). |
22 |
|
23 |
Given that the outer archive is uncompressed tar, every file will be |
24 |
zero-padded to a full block which adds some amount of bloat. So, could |
25 |
the signature be inlined in the Manifest file? That's also what GLEP 74 |
26 |
specifies. |
27 |
|
28 |
Also, IIRC one of the goals of the format was to allow partial download |
29 |
of metadata. That will only work if the Manifest file will be the first |
30 |
file in the archive (or at least appear before the image archive). |
31 |
|
32 |
> +The implementation follows the Manifest specifications in GLEP 74 |
33 |
> +[#GLEP74]_ and uses the DATA tag for files within the archive. |
34 |
|
35 |
AFAICS, GLEP 74 specifies an OpenPGP cleartext signature in the file |
36 |
itself, not a detached signature. |
37 |
|
38 |
Ulrich |