Am 16.11.2005 um 18:53 schrieb Phillip J. Eby: >> Again, not everybody is using distribution processes >> built around CVS or Subversion. Left aside that there >> are quite a few other SCM tools out there, you also have >> the case where you create distributions from plain >> directories (which is what MANIFEST.in and MANIFEST >> are targetting). > > The source control is a supplement to the "add_defaults" of the sdist > process, not a replacement for MANIFEST.in. Some users need to add > non-source-controlled files, for example. But *simple things > should be > simple*, and treating source control info as part of the defaults > makes > them work simply for most people. And if you don't want the defaults, > there should be only one way to turn them off - by excluding files in > MANIFEST.in, not by a command line option.
I'm not sure I understand this proposal completely, but I don't think it's a good idea to have a project's build/setup process rely on having version control meta-data around. Wouldn't that mean that the built package would be incorrect when the setup is run from an `svn export`ed (or otherwise cleaned up) copy? Cheers, Chris -- Christopher Lenz cmlenz at gmx.de http://www.cmlenz.net/ _______________________________________________ Distutils-SIG maillist - [email protected] http://mail.python.org/mailman/listinfo/distutils-sig
