[Grok-dev] Grok 1.1 important issues
vincent.fretin at gmail.com
Sat Feb 27 08:56:21 EST 2010
Site : http://vincentfretin.ecreall.com
On Sat, Feb 27, 2010 at 1:33 PM, Jan-Wijbrand Kolman
<janwijbrand at gmail.com> wrote:
> Vincent Fretin <vincent.fretin at gmail.com> wrote:
>> Actually, even with
>> zopeskel grok grokversion=1.1rc1 MyProject
>> it downloads the big tarball I don't need because I already have all
>> the packages... :-(
> Frankly, I have never been fully convinced of the implementation and
> usefulness of the big tarball. But, having it downloaded when you
> actually have all the eggs already should really be avoided.
> Could you make this into a launchpad bug report?
> regards, jw
Ok, no it's not a bug. I took a look how the eggbasket recipe works.
I didn't have grok 1.1rc1 and grokcore.viewlet 1.4 downloaded or
installed, so it downloaded the tarball. So it's normal.
You can create a grok 1.1rc1 project with one of the following commands:
paster create -t grok MyProject grokversion=1.1rc1
zopeskel grok grokversion=1.1rc1 MyProject
grokproject --grokversion=1.1rc1 MyProject
The big grok-eggs-1.1rc1.tgz tarball is downloaded if the grok package
or one of its dependencies can't be found in ~/.buildout/eggs or in
While the tarball can be good when the user never downloaded any eggs
(the two previous directories are empty),
it is almost unnecessary when you only need to download some new eggs,
when you almost have all eggs already installed or downloaded.
The grok 1.1rc1 tarball only include pytz-2010b-py2.5.egg, not the
sdist, I don't know why...
so if you create a grokproject with Python 2.6 and be sure to remove
previously installed and downloaded
rm -rf ~/.buildout/eggs/pytz-2010b-py2.6.egg
creating a project will really download the tarball for nothing. :)
More information about the Grok-dev