[Zope3-Users] Re: how to eggify a zopeproject?
Hi Jim, > - Eggs are great for distributing libraries. > - They aren't ideal for distributing applications, which are often > composed of many libraries, in the form is eggs. > zc.buildout is a tool for assembling libraries and other parts to > create working applications. (Of course, it is not the only tool.) Ok. That clarifies my ideas. > The zc.sourcerelease package provides a simple script that leverages > buildout to help create self-contained source releases from working > buildouts. This is the tool that I use to distribute applications. Interesting. I'll take a look on this... Thank you for the note. Bye, Nando. -- http://www.nandoquintana.com/contact ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] Re: how to eggify a zopeproject?
Nando Quintana a écrit : Raphael, Either include a MANIFEST file or make the egg from a subversion/cvs checkout. The former tells explicitly what to include the latter implicitly (everything that's under version control basically). This means calling zopeproject with "--svn-repository" ...? this option is just a shortcut that creates a new project in the specified repository. You don't need to pass any option, but just to work in a svn checkout. Any file added via svn will be automatically part of the distribution. Christophe Ok, I'll try it. I'd suggest to look at buildout if you want to support such things as well. So, buildout is the correct approach to deploy an egg as a zope app? Ok. thanks, Nando. ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] Re: how to eggify a zopeproject?
A passing comment: - Eggs are great for distributing libraries. - They aren't ideal for distributing applications, which are often composed of many libraries, in the form is eggs. zc.buildout is a tool for assembling libraries and other parts to create working applications. (Of course, it is not the only tool.) The zc.sourcerelease package provides a simple script that leverages buildout to help create self-contained source releases from working buildouts. This is the tool that I use to distribute applications. Jim On Jan 25, 2008, at 11:25 AM, Nando Quintana wrote: Raphael, Either include a MANIFEST file or make the egg from a subversion/cvs checkout. The former tells explicitly what to include the latter implicitly (everything that's under version control basically). This means calling zopeproject with "--svn-repository" ...? Ok, I'll try it. I'd suggest to look at buildout if you want to support such things as well. So, buildout is the correct approach to deploy an egg as a zope app? Ok. thanks, Nando. -- http://www.nandoquintana.com/contact ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users -- Jim Fulton Zope Corporation ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] Re: how to eggify a zopeproject?
Raphael, > Either include a MANIFEST file or make the egg from a subversion/cvs > checkout. The former tells explicitly what to include the latter > implicitly (everything that's under version control basically). This means calling zopeproject with "--svn-repository" ...? Ok, I'll try it. > I'd suggest to look at buildout if you want to support > such things as well. So, buildout is the correct approach to deploy an egg as a zope app? Ok. thanks, Nando. -- http://www.nandoquintana.com/contact signature.asc Description: Esta parte del mensaje está firmada digitalmente ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
[Zope3-Users] Re: how to eggify a zopeproject?
Nando Quintana wrote: [..] Then I've tried to eggify this zope project: # cd MyProjec # python setup.py sdist The problem is that this action doesn't include the zcml files: Either include a MANIFEST file or make the egg from a subversion/cvs checkout. The former tells explicitly what to include the latter implicitly (everything that's under version control basically). This is documented on PEAK's setup tools site. [..] Then, if a user installs this egg, gets start script "myproject-ctl" installed. Which is the list of thing he need to install? create a zope instance? write a custom zdaemon.comf, deploy.ini, zope.conf, site.zml? I'd suggest to look at buildout if you want to support such things as well. Some general instructions would be very appreciated... HTH Raphael Thanks in advance, Nando. ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users