[Grok-dev] how to manage the versions files, a plan

Ritsjoena bramvandam at gmail.com
Tue Mar 2 07:21:12 EST 2010


Hi,

JW did you already do this or do I have to look for another reason why
my buildouts don't build anymore?

Greetings,
Bram van Dam

Note: due to several reasons we have not migrated beyond 0.14.1 yet.
Martijn Faassen is working on the migration.


On Mar 1, 8:08 pm, Jan-Wijbrand Kolman <janwijbr... at gmail.com> wrote:
> Martijn Faassen <faas... at startifact.com> wrote:
> > Okay, the naming is a bit of a drawback, though it might also discourage
> > people from modifying them directly (instead of modifying a versions
> > section in buildout.cfg), which is good.
>
> > So I'm +1 on going with the extends-cache route for grokproject.
>
> Me is +1 as well.
>
> > Who is volunteering to do the work? :)
>
> I'll adjust grokproject to have it include an extends-cache directive in
> newly generated buildout.cfg files. I'll also revert to the code that used
> to generate an extends directive pointing to the most current version info
> URL. The code that currently would download a versions.cfg can then be
> removed.  I like that: removing code and make things simpler again :-)
>
> Let me also remember to update the upgrade docs for existing projects.
>
> regards,
> jw
>
> _______________________________________________
> Grok-dev mailing list
> Grok-... at zope.orghttps://mail.zope.org/mailman/listinfo/grok-dev


More information about the Grok-dev mailing list