[Zope-dev] zc.buildout not upgrading issue (was Re: RFC: 3.4.1 KGS?)
A: Because it makes the logic of the discussion difficult to follow. Q: Why shouldn't I top post? A: No. Q: Should I top post? On Fri, Apr 02, 2010 at 12:29:48PM +0200, Adam GROSZER wrote: Hello Wichert, Because of our toolchain to release and deploy apps: mypypi and keas.build. In fact, because of keas.build depends on zc.buildout. Friday, April 2, 2010, 10:53:26 AM, you wrote: WA On 4/2/10 10:36 , Adam GROSZER wrote: zc.buildout is a tough decision, because it's not upgrading issue. See http://mail.python.org/pipermail/distutils-sig/2010-March/015794.html WA Why would you ever install zc.buildout systemwide? Just as with WA setuptools I consider that to be a recipe for problems. Why not do python2.x bootstrap.py and then use bin/buildout instead of the globally-installed buildout? Marius Gedminas -- http://pov.lt/ -- Zope 3 consulting and development signature.asc Description: Digital signature ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zc.buildout not upgrading issue (was Re: RFC: 3.4.1 KGS?)
Hello Marius, Friday, April 2, 2010, 3:02:53 PM, you wrote: MG On Fri, Apr 02, 2010 at 12:29:48PM +0200, Adam GROSZER wrote: Hello Wichert, Because of our toolchain to release and deploy apps: mypypi and keas.build. In fact, because of keas.build depends on zc.buildout. Friday, April 2, 2010, 10:53:26 AM, you wrote: WA On 4/2/10 10:36 , Adam GROSZER wrote: zc.buildout is a tough decision, because it's not upgrading issue. See http://mail.python.org/pipermail/distutils-sig/2010-March/015794.html WA Why would you ever install zc.buildout systemwide? Just as with WA setuptools I consider that to be a recipe for problems. MG Why not do MG python2.x bootstrap.py MG and then use MG bin/buildout MG instead of the globally-installed buildout? MG Marius Gedminas The way you install your app with is: $ install -u https://build.twollo.com/buildouts/ -p Twollo -V QA --latest Where the install script comes with keas.build. At this point nothing exists from your app on the server, not even a .cfg or svn checkout. This invokes buildout -c https://build.twollo.com/buildouts/Twollo-QA-2.3.4.cfg -t 2 or something like this. (See http://pypi.python.org/pypi/keas.build/0.1.6 for details) That will gather all necessary packages from (your private) pypi server. And that's why I would need zc.buildout installed globally. It seems to be rather easier to do on a new server: install setuptools $ easy_install zc.buildout==whatever version $ easy_install keas.build $ install my favourite app's install parameters and done I know, doing a checkout and bin/buildout sounds easier, but there's a lot more behind keas.build than just ``install``. The actual problem is that zc.buildout launched by keas.build must be the same version as pinned in the .cfg. A long story... Maybe I just should kick zc.buildout to upgrade itself in the above situation. That would be the best on the long run. -- Best regards, Adam GROSZERmailto:agros...@gmail.com -- Quote of the day: Keep your fears for yourself, but share your courage with others. - Robert Louis Stevenson ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zc.buildout not upgrading issue (was Re: RFC: 3.4.1 KGS?)
On 4/2/10 16:23 , Adam GROSZER wrote: The way you install your app with is: $ install -u https://build.twollo.com/buildouts/ -p Twollo -V QA --latest Where the install script comes with keas.build. At this point nothing exists from your app on the server, not even a .cfg or svn checkout. This invokes buildout -c https://build.twollo.com/buildouts/Twollo-QA-2.3.4.cfg -t 2 or something like this. Perhaps keas.build could be modified to create a virtualenv and install buildout in there? That shouldn't be too hard to do. Wichert. ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zc.buildout not upgrading issue (was Re: RFC: 3.4.1 KGS?)
On Fri, Apr 02, 2010 at 04:23:25PM +0200, Adam GROSZER wrote: MG On Fri, Apr 02, 2010 at 12:29:48PM +0200, Adam GROSZER wrote: Hello Wichert, Because of our toolchain to release and deploy apps: mypypi and keas.build. In fact, because of keas.build depends on zc.buildout. Friday, April 2, 2010, 10:53:26 AM, you wrote: WA On 4/2/10 10:36 , Adam GROSZER wrote: zc.buildout is a tough decision, because it's not upgrading issue. See http://mail.python.org/pipermail/distutils-sig/2010-March/015794.html WA Why would you ever install zc.buildout systemwide? Just as with WA setuptools I consider that to be a recipe for problems. MG Why not do MG python2.x bootstrap.py MG and then use MG bin/buildout MG instead of the globally-installed buildout? MG Marius Gedminas The way you install your app with is: $ install -u https://build.twollo.com/buildouts/ -p Twollo -V QA --latest Where the install script comes with keas.build. Overriding the standard Unix 'install' command is not a good idea IMHO. In fact it's a Bad Idea. At this point nothing exists from your app on the server, not even a .cfg or svn checkout. This invokes buildout -c https://build.twollo.com/buildouts/Twollo-QA-2.3.4.cfg -t 2 or something like this. (See http://pypi.python.org/pypi/keas.build/0.1.6 for details) That will gather all necessary packages from (your private) pypi server. An interesting approach. Looks quite reasonable from first sight. And that's why I would need zc.buildout installed globally. It seems to be rather easier to do on a new server: install setuptools $ easy_install zc.buildout==whatever version $ easy_install keas.build $ install my favourite app's install parameters and done I know, doing a checkout and bin/buildout sounds easier, but there's a lot more behind keas.build than just ``install``. The actual problem is that zc.buildout launched by keas.build must be the same version as pinned in the .cfg. Maybe it would make sense to add a command-line option for buildout to override version pins? bin/buildout -t 2 -c configfile --pin zc.buildout=1.4.3 \ --pin setuptools=0.9c11 with --pin zc.buildout= meaning use latest version, disregarding the pin in the config file. A long story... Maybe I just should kick zc.buildout to upgrade itself in the above situation. That would be the best on the long run. Or that. Marius Gedminas -- http://pov.lt/ -- Zope 3 consulting and development signature.asc Description: Digital signature ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zc.buildout not upgrading issue (was Re: RFC: 3.4.1 KGS?)
On Fri, Apr 2, 2010 at 10:51 AM, Marius Gedminas mar...@gedmin.as wrote: Maybe it would make sense to add a command-line option for buildout to override version pins? bin/buildout -t 2 -c configfile --pin zc.buildout=1.4.3 \ --pin setuptools=0.9c11 with --pin zc.buildout= meaning use latest version, disregarding the pin in the config file. Already implemented: bin/buildout -t 2 -c configfile \ versions:zc.buildout=1.4.3 \ versions:setuptools=0.9c11 -Fred -- Fred L. Drake, Jr.fdrake at gmail.com Chaos is the score upon which reality is written. --Henry Miller ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zc.buildout not upgrading issue (was Re: RFC: 3.4.1 KGS?)
On Friday 02 April 2010, Marius Gedminas wrote: Why not do python2.x bootstrap.py and then use bin/buildout instead of the globally-installed buildout? I definitely hear you. On the other hand, I think of buildout as a replacement for make. And I would not want to install a special make either on a machine. They key here is that the deployment and staging servers have very minimal setups. And there you just want to install a package that gets you going. Regards, Stephan -- Entrepreneur and Software Geek Google me. Zope Stephan Richter ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
