[Letsencrypt-devel] PyPi vs Git

[Francois Marier]

On 2015-10-06 19:09, Harlan Lieberman-Berg wrote:
> With the first tarball release out from Let's Encrypt, it seems we've
> run into a bit of a problem.  Prior to this, in git, we've been working
> off of the assumption that we would be getting a single, monolithic
> tarball.  With the release to PyPi, though, now all of the binary
> packages that we have been building are in separate source packages.

I only see two source packages:

   https://pypi.python.org/pypi/letsencrypt/0.0.0.dev20151006
   https://pypi.python.org/pypi/acme

which suggests to me that letsencrypt-doc and letsencrypt-apache would 
be binary packages of letsencrypt.

> 1.  Create separate source packages for all of the binary packages, and
> figure out the logical way to install the docs (probably as a second
> binary package off of the main letsencrypt client).

If we're only dealing with the above two, that sounds like the logical 
approach. I imagine at some point that python-acme will not need to be 
released at the same time as letsencrypt.

> 2.  Assemble the tarballs into a single tree, and then use that as the
> source orig.tar.gz for a single source package.  We have to be a bit
> careful when merging them, since some of the files themselves may need
> to be interleaved.

That's my least preferred option.

> 3.  Use signed tags from git, instead of the bundles sent to PyPi.

Well, if splitting the packages is a one-time thing, I don't really 
mind. It means we'll need another repo and we'll upload that separately, 
but it matches more closely how upstream views the software they ship.

Francois