On Aug 20, 2009, at 9:25 AM, Brandon Craig Rhodes wrote: > Our experience with Grok was that the product broke roughly every > other > week (and sometimes even a bit more often than that) because people > would release new versions of things with which we wound up being > somehow incompatible. Only by pinning versions exactly with "==" were > we able to assure that a Grok site deployed successfully today would > successfully deploy next week. Otherwise, a web site deployed to > three > different servers over a period of, say, three weeks, wound really be > three slightly different web sites instead of being identical. :-) > > But, yes, it causes a headache when building a site out of several > different pieces. :-/
I guess there's no silver bullet. But the annoying bit about the getpaid recipe is that even if I *know* a particular version of five.intid works with both getpaid and something else, there's no way I can force it to use something different than the version that is encoded in getpaid.recipe.release. I'd love to see getpaid stop using its special recipe and move to pinning its dependencies via extending the versions block of a known good set, like most other large Zope-based frameworks (Zope itself, Plone, dexterity) are doing these days. David --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "getpaid-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/getpaid-dev?hl=en -~----------~----~----~----~------~----~------~--~---
