<div dir="ltr">@Leonardo,<br>I think that would be valuable. I personally know that certain universities have draconian firewall setups that are just not friendly to the pypi way of installing software. It certainly would help for a newbie to be able to download a single tarball via a normal "http" connection.<br>
<br><div class="gmail_quote">On Tue, Sep 16, 2008 at 7:27 PM, Leonardo Rochael Almeida <span dir="ltr"><<a href="mailto:leorochael@gmail.com">leorochael@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
May I suggest a tarball?<br>
<br>
Eggbasket is cool and all, but I think a Grok release should include a<br>
tarball. This could be just a buildout with built-in download cache<br>
that can be setup by running "python bootstrap.py; bin/buildout -No"<br>
(or, better yet, "python install.py"), and it should contain all<br>
dependencies not present in the python standard library for grok AND<br>
for grokproject.<br>
<br>
This buildout tar should build grokproject in its ./bin, and this<br>
grokproject should create buildouts based on the eggs already present<br>
on the tarball and configuring "newest=false" in buildout.cfg, so that<br>
downloading the tarball is the only operation needing network access<br>
before you can try out grok.<br>
<br>
Perhaps a tarball that creates a virtualenv instead of wrapping a<br>
grok/grokproject buildout would be easier, or maybe some other python<br>
package that creates tarballs out of buildouts, but the point is that<br>
installing Grok should never be more complicated or error prone than,<br>
to pick a completely random example out of my hat :-), Django[1].<br>
<br>
Right now, even with eggbasket, we still need a number of things to be<br>
"Just Right On The Internet" for Grok to "Just Work" for someone,<br>
including a number of packages being on their right versions, as it<br>
seems like even version pinning is not sufficient to keep us safe from<br>
things that could break grokproject itself. I'd rather have the user<br>
just download one package beyond python itself to be able to get up<br>
and running with Grok.<br>
<br>
Cheers, Leo<br>
<br>
[1] <a href="http://www.djangoproject.com/download/" target="_blank">http://www.djangoproject.com/download/</a><br>
<br>
To save you guys a browser trip, the installation process is:<br>
<br>
* download and open tarball<br>
* run "python setup.py install"<br>
* use the installed scripts to create a new 'django package', which<br>
won't need anything else to be downloaded before it can be run with<br>
the built-in http server.<br>
<div class="Ih2E3d"><br>
On Tue, Sep 16, 2008 at 20:36, Martijn Faassen <<a href="mailto:faassen@startifact.com">faassen@startifact.com</a>> wrote:<br>
> Hi everybody,<br>
><br>
> The summer is over, I moved house, it's time to look at a Grok 0.14 release.<br>
><br>
</div>> [...]<br>
<div><div></div><div class="Wj3C7c">> Any items that are in progress on the trunk right now and haven't been<br>
> finished yet?<br>
><br>
> Shall we set a release date for Grok 0.14 later this month/early october?<br>
><br>
> This also ties into grokproject; recently I posted a list of issues with<br>
> it and I hope we can release a new version of grokproject (and<br>
> eggbasket, etc) that fixes some of these soon.<br>
><br>
> Regards,<br>
><br>
> Martijn<br>
_______________________________________________<br>
Grok-dev mailing list<br>
<a href="mailto:Grok-dev@zope.org">Grok-dev@zope.org</a><br>
<a href="http://mail.zope.org/mailman/listinfo/grok-dev" target="_blank">http://mail.zope.org/mailman/listinfo/grok-dev</a><br>
</div></div></blockquote></div><br></div>