[Pkg-anonymity-tools] torbrowser-launcher in Debian stable [Was: annotated tag debian/0.1.8-1 created (now 1e9ff2c)]

[u]

Hi,

Holger Levsen:
> On Mittwoch, 21. Januar 2015, intrigeri wrote:

[...]

>> Long-term wise, we should probably split the package between code
>> (that would be frozen in Debian stable) and data (that could be
>> updated as needed). However, some logic that needs to be updated from
>> time to time (e.g. alpha/beta detection) lives in the code, so it
>> would need to be parameterized (e.g. the corresponding regexp), and
>> the paramaters would need to be extracted from the Python code to some
>> configuration file that we could put in the data package. It's of
>> course too late to do that for Jessie, but it would be good to file
>> a request upstream about it so that we don't realize once Stretch is
>> frozen that it didn't happen yet :)

If I understand your idea correctly, this might be the cleaner way to do
it. Would this only apply for the stable package then?

However, there seems to be a 3rd parameter to be taken into account,
which is the way the Torporject itself handles their signing keys,
certificates, version numbers and URLs (this is not merely a list of
examples, but actual updates we've had in the past on this package).

Until now, I always had the impression that this is not very clear and
there is no communication whatsoever (even if one reads tor-qa), so that
modifications on the Torproject side arrive quite late in tbl and arrive
even later on our plate.

So all this information and other stuff we did not anticipate yet would
need to go into that data package you are suggesting, correct?

> Given the above and the nature of the package (it's tiny and has a single 
> purpose) I'm not sure its worth the effort. Also I hope that it will become 
> more stable in the next two years :-)

Maybe Micah already has an opinion or plans for the future and can tell
us if he thinks it's worth the effort?

Cheers!
u.