Re: [Letsencrypt-devel] Package Name Change

[Harlan Lieberman-Berg]

Francois Marier  writes:
> If they ever change the "import" name, then we should probably rename 
> the binary packages, but in the meantime, it's probably less confusing 
> to stick with the existing names.

The latest update is that they are going to be changing the module
names.

It's now certbot and certbot-apache.  So, I'm thinking... letsencrypt
and letsencrypt-apache Provided by certbot and certbot-apache, and then
Breaks/Replaces as necessary?

Sincerenly,
-- 
Harlan Lieberman-Berg
~hlieberman

___
Letsencrypt-devel mailing list
Letsencrypt-devel@lists.alioth.debian.org
https://lists.alioth.debian.org/mailman/listinfo/letsencrypt-devel

Re: [Letsencrypt-devel] Package Name Change

[Francois Marier]

On 2016-04-11 07:33, Harlan Lieberman-Berg wrote:

At this point, it looks like the python modules will be changing the
distribution name, but not the actual module name (i.e., pip install
, but import letsencrypt).  If that stays the same, I think
it's probably OK for us to leave the name of python-letsencrypt alone.

I think we should turn letsencrypt into a virtual package and Provide 
it

from .  I'm not 100% sure what to do with the
python-letsencrypt-apache module, though.  It /is/ technically user
facing, in that you need to install that module to have the
functionality and we don't Recommend it (since that would pull in
apache2).  But it also seems a bit strange to have a package 
python-
name>-apache which installs an actual module named letsencrypt-apache.
I suppose we could do something with a virtual package here 
(python-
name>-apache Provides python-letsencrypt-apache), but...

I'd appreciate some advice here.  What do you all think?


Can't we just keep python-letsencrypt-apache since that's the name that 
actually matters to users?


If they ever change the "import" name, then we should probably rename 
the binary packages, but in the meantime, it's probably less confusing 
to stick with the existing names.


Francois

___
Letsencrypt-devel mailing list
Letsencrypt-devel@lists.alioth.debian.org
https://lists.alioth.debian.org/mailman/listinfo/letsencrypt-devel

[Letsencrypt-devel] Package Name Change

[Harlan Lieberman-Berg]

Hello everyone.

I've been in discussion with upstream for the last couple of weeks about
the upcoming name change, which should come with the 0.6.0 or 0.7.0
release.

At this point, it looks like the python modules will be changing the
distribution name, but not the actual module name (i.e., pip install
, but import letsencrypt).  If that stays the same, I think
it's probably OK for us to leave the name of python-letsencrypt alone.

I think we should turn letsencrypt into a virtual package and Provide it
from .  I'm not 100% sure what to do with the
python-letsencrypt-apache module, though.  It /is/ technically user
facing, in that you need to install that module to have the
functionality and we don't Recommend it (since that would pull in
apache2).  But it also seems a bit strange to have a package python--apache which installs an actual module named letsencrypt-apache.
I suppose we could do something with a virtual package here (python--apache Provides python-letsencrypt-apache), but...

I'd appreciate some advice here.  What do you all think?

Sincerely,

-- 
Harlan Lieberman-Berg
~hlieberman

___
Letsencrypt-devel mailing list
Letsencrypt-devel@lists.alioth.debian.org
https://lists.alioth.debian.org/mailman/listinfo/letsencrypt-devel