[Distutils] Deprecate MANIFEST.in

[Tres Seaver]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

David Cournapeau wrote:
> Ben Finney wrote:
>> An sdist is *not* just a tarball of the source files.
> 
> It is if you consider any non-tracked file to be an anti-usecase, which
> is what I was answering to :)

There are three classes of files here:

- - "source" files, which should be under version control, and included
  (by default) in the sdist.

- - "derived" files, which should *not* be under version control, but
  which might (in certain circumstances) be included in the sdist.
  E.g., the C file generated from a Pyrex / Cython source file, to
  enable builds on systems without Pyrex / Cython installed.

- - "stray" files, not under version control.  These shuold *never* be
  in an sdist.

Some way of spelling exceptions to the rule "include all files under
source control, and only those under source contrl" is useful (this is
what MANIFEST.in does under setuptools, accordign to PJE).  The default
rule, which would apply in the 95% case, should be fine.

> Moving away from "using VCS is good" vs "using VCS is not good", maybe
> we should focus on the workflows to support. The most significant to me
> is reproducibility (python setup.py sdist output should depend as little
> as possible on its environment - whether the sources are under VCS or
> not, etc....). At least one person said this is not a requirement. Can
> we reach a consensus on this point, and then focus on the technical
> solutions ?

I don't understand the goal of "not depending on the environment" (it
will depend on the version of Python / distutils / setuptools / Cython /
Pyrex you use, for instance, just as C-based packages depend on the
version of autogen and any local autoconf macros).  I do know that
making packagers maintain manifests leads trivially to broken sdists.


Tres.
- --
===================================================================
Tres Seaver          +1 540-429-0999          tseaver at palladion.com
Palladion Software   "Excellence by Design"    http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFJ225H+gerLs4ltQ4RAjHzAKDYyW1wpPezB5F3eGWs0iRctUT4HwCfSJI7
p35LqrFxsRe8RsfUyLDyo6Q=
=cwfT
-----END PGP SIGNATURE-----