On Jul 17, 2006, at 2:35 PM, Phillip J. Eby wrote: > At 07:17 AM 7/17/2006 -0700, Bob Ippolito wrote: >> It seems that --no-svn-revision is only part of the solution to >> making releases less of a hassle. The problem is that setup.cfg is >> still included in sdist, so any user that builds your egg from source >> is going to have it tagged with ".dev_r0". This is especially >> problematic for dependencies because it may download the correct >> version of source, but ".dev_r0" ranks lower so it will say the >> dependency is not satisfied. >> >> What's the best solution to this, barring deleting setup.cfg from the >> release branch? > > Argh. Well, you could put an exclude in MANIFEST.in to drop the > setup.cfg, but that sucks. Maybe the right thing to do is to > include the setup.cfg, but to update it with the tag and version > settings that were in effect when the sdist was built.
That's not a bad idea (update setup.cfg on sdist w/ --no-svn- revision). Any chance of getting this in setuptools 0.6 or should I start adding MANIFEST.in files to the relevant projects? -bob _______________________________________________ Distutils-SIG maillist - [email protected] http://mail.python.org/mailman/listinfo/distutils-sig
