[Grok-dev] UPDATE recently created projects to 0.14.1

Brandon Craig Rhodes brandon at rhodesmill.org
Sun Dec 14 08:46:02 EST 2008


I understand that our policies prevent us from fixing 0.14 itself
retroactively and protecting people with old buildouts who haven't seen
all of the announcements; we want to keep everything old looking like it
always did so that old buildouts can always be guaranteed to be
identical, even if identically insecure.

But it would be nice to display a message.

Before 1.0, could we add to "grokproject" a line that, if it's using its
default URL, also looks up another URL and, if it exists, prints the
message there?  The idea is that when downloading:

   http://grok.zope.org/releaseinfo/grok-0.14.cfg

it would also check for, and expect a 404 from, the URL:

   http://grok.zope.org/releaseinfo/grok-0.14.WARNING.txt

But if it did find a text file at that URL, then it waits until it
finishes its run (to avoid having the crucial message scrolling off the
screen!) and then prints the message that it found there.

That way, old-buildout-identicalness would be preserved, but users would
at least have some indication that they needed to take action if they
did not want their site to be invaded.

-- 
Brandon Craig Rhodes   brandon at rhodesmill.org   http://rhodesmill.org/brandon


More information about the Grok-dev mailing list