On Thursday 12 August 2010 15:03:23 Данило Шеган wrote:
> Jeroen, I think you are mistaken here. Soyuz "custom" upload is an
> actual upload of the tarball which contains translations (I am not sure
> if it contains full source code as well, but that's not really
> relevant).
Custom uploads are defined as anything that has a "custom" file attached
(translations fall into that category).
> If debs actually included PO files, that'd be very weird, and
> they'd have to be there without being installed, but would still take a
> lot of disk space on Ubuntu live CDs eg.
>
> Also, while debs are based on tarballs, they are not really ones. They
> are tarballs wrapped with some binary data (or something like that), so
> our code wouldn't even work if this was the case. FWIW, I've tried and
> even tarfile.is_tarfile() returns False for .deb files.
On Thursday 12 August 2010 15:03:23 Данило Шеган wrote:
> Jeroen, I think you are mistaken here. Soyuz "custom" upload is an
> actual upload of the tarball which contains translations (I am not sure
> if it contains full source code as well, but that's not really
> relevant).
Custom uploads are defined as anything that has a "custom" file attached
(translations fall into that category).
> If debs actually included PO files, that'd be very weird, and is_tarfile( ) returns False for .deb files.
> they'd have to be there without being installed, but would still take a
> lot of disk space on Ubuntu live CDs eg.
>
> Also, while debs are based on tarballs, they are not really ones. They
> are tarballs wrapped with some binary data (or something like that), so
> our code wouldn't even work if this was the case. FWIW, I've tried and
> even tarfile.
A deb is actually a gnu "ar" archive :)
Try "ar t <file.deb>"