1 |
>>>>> On Mon, 26 Nov 2018, Michał Górny wrote: |
2 |
|
3 |
> Specification |
4 |
> ============= |
5 |
|
6 |
> The container format |
7 |
> -------------------- |
8 |
|
9 |
> The gpkg package container is an uncompressed .tar achive whose filename |
10 |
> should use ``.gpkg.tar`` suffix. This archive contains the following |
11 |
> members, all placed in a single directory whose name matches |
12 |
> the basename of the package file, in order: |
13 |
|
14 |
I see no value in adding another directory indirection, and it will add |
15 |
more overhead. Also, AFAICS the tar|tar pipeline that you previously |
16 |
suggested won't work any more (or would at least require additional |
17 |
arguments). |
18 |
|
19 |
> 1. The package identifier file ``gpkg-1.txt`` (required). |
20 |
|
21 |
> [...] |
22 |
|
23 |
> The implementations must include a package identifier file named |
24 |
> ``gpkg-1.txt``. The filename includes package format version; |
25 |
> implementations should reject packages which do not contain this file |
26 |
> as unsupported format. |
27 |
|
28 |
> The file can have any contents. Normally, it should be empty. |
29 |
|
30 |
If the file is empty, why is it named gpkg-1.txt (instead of just |
31 |
gpkg-1)? |
32 |
|
33 |
Ulrich |