[Pkg-privacy-maintainers] Torbirdy packaging workflow

[u]

Hi,

as mentioned by intrigeri (see quote hereafter) on this list, we should
talk about a workflow which all of us and future contributors can easily
adopt if they want to help with torbirdy.

> There were 4 different packaging methods documented in d/README.source
> already, and now we have 5. Wow. Of course it's not your (U's) duty to
> fix that situation. Still, note that commit daf8289 will break those,
> among the documented workflows, that use upstream's Git tag instead of
> their XPI; this commit is essentially reverting Lunar's e14bdc7, that
> I think he did so that he could use his preferred workflow. So the
> revert "war" has already started, and next time someone wants to use
> a Git-tag-without-XPI workflow, they'll need to revert the revert.
> That's not a blocker for this upload, but I suggest you folks discuss
> this topic and find out a way that works for everybody who's working
> on this package :)

This new workflow should replace the 4 different ones on the
debian/README.source.

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.

What do others think, and I'd be particularly interested in opinions of
Lunar and Ximin because they maintain other XUL / FF extensions in Debian.

Cheers!
u.