[Grok-dev] Towards Grok 0.14

[David Bain]

@Leonardo,
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.

On Tue, Sep 16, 2008 at 7:27 PM, Leonardo Rochael Almeida <
leorochael at gmail.com> wrote:

> May I suggest a tarball?
>
> Eggbasket is cool and all, but I think a Grok release should include a
> tarball. This could be just a buildout with built-in download cache
> that can be setup by running "python bootstrap.py; bin/buildout -No"
> (or, better yet, "python install.py"), and it should contain all
> dependencies not present in the python standard library for grok AND
> for grokproject.
>
> This buildout tar should build grokproject in its ./bin, and this
> grokproject should create buildouts based on the eggs already present
> on the tarball and configuring "newest=false" in buildout.cfg, so that
> downloading the tarball is the only operation needing network access
> before you can try out grok.
>
> Perhaps a tarball that creates a virtualenv instead of wrapping a
> grok/grokproject buildout would be easier, or maybe some other python
> package that creates tarballs out of buildouts, but the point is that
> installing Grok should never be more complicated or error prone than,
> to pick a completely random example out of my hat :-), Django[1].
>
> Right now, even with eggbasket, we still need a number of things to be
> "Just Right On The Internet" for Grok to "Just Work" for someone,
> including a number of packages being on their right versions, as it
> seems like even version pinning is not sufficient to keep us safe from
> things that could break grokproject itself. I'd rather have the user
> just download one package beyond python itself to be able to get up
> and running with Grok.
>
> Cheers, Leo
>
>  [1] http://www.djangoproject.com/download/
>
>  To save you guys a browser trip, the installation process is:
>
>   * download and open tarball
>   * run "python setup.py install"
>   * use the installed scripts to create a new 'django package', which
> won't need anything else to be downloaded before it can be run with
> the built-in http server.
>
> On Tue, Sep 16, 2008 at 20:36, Martijn Faassen <faassen at startifact.com>
> wrote:
> > Hi everybody,
> >
> > The summer is over, I moved house, it's time to look at a Grok 0.14
> release.
> >
> > [...]
> > Any items that are in progress on the trunk right now and haven't been
> > finished yet?
> >
> > Shall we set a release date for Grok 0.14 later this month/early october?
> >
> > This also ties into grokproject; recently I posted a list of issues with
> > it and I hope we can release a new version of grokproject (and
> > eggbasket, etc) that fixes some of these soon.
> >
> > Regards,
> >
> > Martijn
> _______________________________________________
> Grok-dev mailing list
> Grok-dev at zope.org
> http://mail.zope.org/mailman/listinfo/grok-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.zope.org/pipermail/grok-dev/attachments/20080916/840aa911/attachment.html