-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
Hi Erinn,
it would be great if there was a canonical path to tor alpha releases (like the RPM repo provides) so people that choose to use alpha releases would not have to change their apt sources.list as soon as a new major tor version is released.
What do you think about #14997? https://trac.torproject.org/projects/tor/ticket/14997
I guess this would not be big effort - simply creating a subfolder for the alpha builds would do it?
thanks, Nusenu
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
What do you think about #14997? https://trac.torproject.org/projects/tor/ticket/14997
I guess this would not be big effort - simply creating a subfolder for the alpha builds would do it?
Ok, I just saw that weasel closed it as a wontfix - the same moment as I wrote this email.
weasel wrote:
Running the current alpha should always be a deliberate decision.
If you can't be bothered to change your sources.list once or twice a year, then you probably should be running stable.
Maybe explaining my use case/motivation will make it more clear why this is not about changing the sources.list once a year.
I wrote an ansible role [1] where the user can opt-in for alpha releases by setting a boolean. So this is already a user decision.
By taking the user's decision into account I generate the appropriate sources.list entry, but if the sources.list entry for alpha releases is not static this will break over time.
I could do some "lets find out current stable and do stableversion + 1" but that will also break because currently the latest stable is 0.2.6.6 but there is no such repo as https://deb.torproject.org/torproject.org/dists/tor-experimental-0.2.7.x-jes...
Generally speaking it would just be a lot cleaner on my side if there would be such a static place to go for alpha releases.
regards, Nusenu
[1] https://github.com/nusenu/ansible-relayor
-
Nusenu