[Grok-dev] grok trunk - buildout broken

[Tim Cook]

Of course I only speak for myself and not as a core Grok developer.  But
with the churn going on in the Zope community and the constant issuing
of new releases of COMPONENTS vs. complete systems.  I think that any
platform MUST pin versions of components as known good.   

IMHO, this is very much in keeping with the philosophy of KGSs in Zope
today.

--Tim 

On Mon, 2009-05-18 at 21:56 +0200, Jan-Wijbrand Kolman wrote:
> Wichert Akkerman wrote:
> > Previously Jan-Wijbrand Kolman wrote:
> >> Right, it currently is, and apparently needed for running the tests. I
> >> think grokcore.view should pin a version for it. And grok should do the
> >> same thing - a it does so, I see now.
> > 
> > Please no - packages should never pin exact versions.
> 
> Are you saying the versions.cfg of neither grok nor grokcore.view should
> specify ("pin") the version of zope.container, as I just did? Mind you,
> I did *not* change requirements in either setup.py files.
> 
> In other words, are we talking about the same thing here? Maybe I'm
> using misguided meanings of "pinning" here..?
> 
> regards,
> jw
> 
> _______________________________________________
> Grok-dev mailing list
> Grok-dev at zope.org
> http://mail.zope.org/mailman/listinfo/grok-dev
-- 
Timothy Cook, MSc
Health Informatics Research & Development Services
LinkedIn Profile:http://www.linkedin.com/in/timothywaynecook 
Skype ID == timothy.cook 
**************************************************************
*You may get my Public GPG key from  popular keyservers or   *
*from this link http://timothywayne.cook.googlepages.com/home*
**************************************************************
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
Url : http://mail.zope.org/pipermail/grok-dev/attachments/20090518/b7db9f62/attachment.bin