-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 08/21/2013 07:27 PM, Toshio Kuratomi wrote:
On Wed, Aug 21, 2013 at 02:09:33AM -0400, Bohuslav Kabrda wrote:
----- Original Message -----
Greetings everyone, we had a productive session at flock and actually covered everything that was in my email message about a potential agenda. Here's the notes:
https://fedoraproject.org/wiki/User:Toshio/Flock2013_Python_Guidelines
Thanks for posting this, Toshio. Few comments:
- The wheel proposal seems nice, although we should probably also
cover the case where upstream _only_ distributes wheel and not tarball (shouldn't be a big deal).
I'll have to look into this a bit. I'm not certain that a wheel contains all the source. I'm almost certain that it wouldn't fit under "preferred form of modification". Depending on those, we might want to tell people tarballs, followed by source checkouts are prefered/okay. Wheels might be third on the list or might be banned as a Source: line.
Wheels are a binary format from an upstream point of view. I certainly wouldn't consider them a suitable input format for an SRPM.
The Python world has 3 source distribution formats:
- - raw tarball - - VCS checkout - - sdist
The difference between an sdist and a raw tarball is that the sdist may be a filtered version of what's in the source repo. This may happen if the repo contains additional files that aren't needed to build and install the distribution. If an archive has a PKG-INFO file at the root, it's likely an sdist, if it doesn't, it's likely a raw tarball.
Cheers, Nick.
- -- Nick Coghlan Red Hat Infrastructure Engineering & Development, Brisbane
Testing Solutions Team Lead Beaker Development Lead (http://beaker-project.org/)