-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Wichert Akkerman wrote: > Previously Maurits van Rees wrote: >> Wichert Akkerman, on 2008-05-29: >>> Previously Maurits van Rees wrote: >>>> Wichert Akkerman, on 2008-05-29: >>>>> Previously Maurits van Rees wrote: >>>>>> Wichert Akkerman, on 2008-05-29: >>>>>>> Previously Philipp von Weitershausen wrote: >>>>>>>>> But personally I like having it inside the "main" >>>>>>>>> folder, so in your example above it would be >>>>>>>>> incf.applications/incf/applications/HISTORY.txt >>>>>>>> There's some benefit to that because it'll be part of the egg. >>>>>>> You probably want to use a MANIFEST.in anyway and that can easily be >>>>>>> used to include everything in doc/ or other places. >>>>>> A 'python setup.py sdist' will include the docs directory, as long as >>>>>> it is in subversion (and has at least one file in it). >>>>> And when someone installs from that sdist and there is no MANIFEST.in >>>>> you suddenly end up with installs which are missing data files, zcml >>>>> files or other things. >>>> Is there a difference in that regard between easy installing an sdist >>>> or a bdist_egg? I would think/hope that the end result is the same. >>> Yes. If you make the bdist_egg from a svn checkout it includes all files >>> that are in subversion. If you make an egg from something else like a >>> sdist or a svn export that does not happen (since the svn information is >>> not available). >> Without a MANIFEST.in, the egg resulting from an sdist that is >> easy_installed is the same as a bdist_egg, right? Indeed when I try >> that for plone.portlet.static this is the case. So having a >> MANIFEST.in makes no real difference in that regard. > > I'm not sure what you mean. The basic algorihm is: > > - MANIFEST is used to determine what is installed, or > - subversion workingcopy information is used to determine what is installed, > or > - a default ruleset is used > > This algorithm is used at the moment a 'binary installation' is made, > which is either when you build an egg using setup.py bdist_egg or when > you install an egg from source (ie from a sdist or an unpacked tree).
setuptools-generated sdist tarballs made from SVN checkouts get all the correct files in them when made into eggs / installed via setuptools, using the metadata in the .egg-info directory (SOURCES.txt, in particular). I think the only issue is for folks who would like to install your packages without having setuptools present. Voluntarily using bare distutils is already so masochistic that I don't feel much pity for the added pain. Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 [EMAIL PROTECTED] 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 iD8DBQFIPvyA+gerLs4ltQ4RArTOAJ41EZT9T5oCXhlOOetfheckYEzS9gCghto7 ZXOQYIjFxkfJzugcLN7Gb+Y= =vZQp -----END PGP SIGNATURE----- _______________________________________________ Zope-CMF maillist - Zope-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See http://collector.zope.org/CMF for bug reports and feature requests