Op 28-05-10 10:30, toutpt schreef: > > Hi, > > Following the last thread I have added a manifest.in to collective.gallery, > but ... > > I have read some documentation and discuss about it with kiorky who think > that manifest.in must not be used and is error prone. I'm agree with him > that you can easily forgot some extension like jpeg or what ever. > > So I have check the plone code and their is no manifest.in. Do that means it > must not to be used ?
What I have usually seen is: recursive-include collective * global-exclude *pyc I have not experimented with it and I do not usually add such a MANIFEST.in file myself. If you know your environment is setup correctly, you do not need it. But correctly setup means that when using subversion 1.5 or higher you need a recent setuptools (0.6c11 I think) or distribute. And when using git/mercurial/bazaar, you need an extra package installed that tells setuptools/distribute/distutils/whatever how to know which files should be included. See pypi for the packages setuptools-git and setuptools_hg. And you should not make a release from a subversion export, but only from a subversion checkout, otherwise the info about which files should be there is gone. -- Maurits van Rees Programmer, Zest Software _______________________________________________ Product-Developers mailing list [email protected] http://lists.plone.org/mailman/listinfo/product-developers
