On Sat, 19 Mar 2016 11:46:41 +0100 Johannes Schauer <[email protected]> wrote: > I require none of these packages and they will just take up space on a > system where I have no need for being able to acquire a certificate via > letsencrypt ever.
I was also thinking of removing it to be able to run it on jessie as I had trouble backporting letsencrypt. (Btw I have backported it on jessie and it is running on https://git.pxq.in). But I figured out letsencrypt is already backported to jessie. I will see if I can use a ruby gem to do the same (acme-client https://rubygems.org/gems/acme-client is one candidate) so we can avoid a lot of python libraries. > It also seems that letsencrypt is only used in the postinst script if > the respective debconf variable is set to true. Thus it seems that the > availability of letsencrypt is actually optional and not a hard > dependency of the gitlab system. I'd like to give the option to use letsencrypt by default for those who wish to use. > Considering these points, could you maybe move the letsencrypt > dependency from Depends into Recommends and adjust the postinst script > to only try using letsencrypt if the binary is available? > If I manage to use a small gem for this purpose I think it won't be a big problem to have it around.
signature.asc
Description: OpenPGP digital signature
