grok buildout itself should use paster

Bug #307197 reported by Martijn Faassen on 2008-12-11
2
Affects Status Importance Assigned to Milestone
grok
Medium
Michael Haubenwallner
1.0
Medium
Michael Haubenwallner

Bug Description

Since paster is going to be the default way that grokproject uses to start grok, we should change the buildout that comes
with grok to install grok itself (and grokwiki) this way as well.

Martijn Faassen (faassen) wrote :

Brandon, feel free to coordinate this with Michael Haubenwallner (d2m on launchpad) - perhaps you can reassign to him. I'm just assigning to you as you're currently driving the grokproject stuff.

Changed in grok:
assignee: nobody → brandon-rhodes
importance: Undecided → Medium
milestone: none → 1.0
status: New → Confirmed
Brandon Rhodes (brandon-rhodes) wrote :

I built a Grok project with the new "grokproject"; I created a new directory with just buildout.cfg, bootstrap.py, setup.py, versions.cfg, and src/<app>/* from the original project; and after re-running bootstrap and buildout, the commands bin/g-debug, bin/g-ctl, and bin/paster (yay!) were all available. Does this mean that I can mark this bug as fixed?

Michael Haubenwallner (d2m) wrote :

Ready to commit the new paster based layout

Waiting for http://svn.zope.org/zope.publisher/tags/3.4.6.1 to be released (fixes the XMLRPC bug under paster)

Michael Haubenwallner (d2m) wrote :

switched buildout to paster base template (like grokproject default)

http://svn.zope.org/grok/trunk/CREDITS.txt?rev=101438&view=rev

Michael Haubenwallner (d2m) wrote :

switched buildout to paster base template (like grokproject default)

http://svn.zope.org/grok/trunk/?rev=101438&view=rev

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers