| 1 |
On 11/13/18 9:53 AM, Zac Medico wrote: |
| 2 |
> On 11/13/18 9:49 AM, Zac Medico wrote: |
| 3 |
>> On 11/11/18 12:53 PM, Michał Górny wrote: |
| 4 |
>>> Hi, |
| 5 |
>>> |
| 6 |
>>> Ok, here's the second version integrating the feedback received. |
| 7 |
>>> The format is much simpler, based on nested tarballs inspired by Debian. |
| 8 |
>>> |
| 9 |
>>> The outer tarball is uncompressed and uses '.gpkg.tar' suffix. It |
| 10 |
>>> contains (preferably in order but PM should also handle packages with |
| 11 |
>>> mismatched order): |
| 12 |
>>> |
| 13 |
>>> 1. Optional (but recommended) "gpkg: ${PF}" package label that can be |
| 14 |
>>> used to quickly distinguish Gentoo binpkgs from regular tarballs |
| 15 |
>>> (for file(1)). |
| 16 |
>>> |
| 17 |
>>> 2. "metadata.tar${comp}" tarball containing binary package metadata |
| 18 |
>>> as files. |
| 19 |
>>> |
| 20 |
>>> 3. Optional "metadata.tar${comp}.sig" containing detached signature |
| 21 |
>>> for the metadata archive. |
| 22 |
>>> |
| 23 |
>>> 4. "contents.tar${comp}" tarball containing files to be installed. |
| 24 |
>>> |
| 25 |
>>> 5. Optional "contents.tar${comp}.sig" containing detached signature for |
| 26 |
>>> the contents archive. |
| 27 |
>> |
| 28 |
>> We'll want to access "contents.tar${comp}.sig" very early, but in the |
| 29 |
>> absence of an index containing offsets, normally we'd have to read all |
| 30 |
>> of "contents.tar${comp}" first. However, I suppose we could search |
| 31 |
>> backwards for the "contents.tar${comp}.sig" entry. |
| 32 |
> |
| 33 |
> We could solve this problem by adding an index file containing offsets |
| 34 |
> as the last file in the outer tar file. |
| 35 |
|
| 36 |
Actually, the tar entry for "contents.tar${comp}" should contain the |
| 37 |
length, so we should be able to efficiently seek to the |
| 38 |
"contents.tar${comp}.sig" entry. So, an index is not really needed. |
| 39 |
-- |
| 40 |
Thanks, |
| 41 |
Zac |
Archives