[Pkg-privacy-maintainers] Torbirdy packaging workflow

[Jérémy Bobbio]

u:
> I've docmented mine in there too, and it uses the XPI, not upstream Git
> branches. However, I think that both could be used. XPI + uscan and then
> compare the contents with the Git branch.

XPI is not always the preferred form of modification and so not suitable
to be considered the original tarball. One example is HTTPS
Everywhere which ships an SQLite database with rewrite rules that is
created at build time from XML descriptions.

Most often we can get away with using XPI because because they ship the
source code with no translation, but we should not count on it.

-- 
Lunar                                .''`. 
lunar at debian.org                    : :Ⓐ  :  # apt-get install anarchism
                                    `. `'` 
                                      `-   
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-privacy-maintainers/attachments/20151016/85255b37/attachment.sig>