* UPDATE I have commited the changes to the recipe to the repository under getpaide.recipe.release/branches/1.9.1. The versions block is under getpaid.versions. I have tested it and it seems to be working 100%.
Hannes 2009/9/3 hannesc <[email protected]> > > Just to revisit this subject. > > I have updated the recipe on my side and removed the version pinning > from it. Instead I created a versions.cfg file to be use in the build > out. This enables the user to change the version numbers as they see > fit (eg my five.intid problem mentioned previously). They both seem to > be working perfectly. Where can I submit these for review? > > Thanks > Hannes > > On Aug 21, 5:09 am, Hannes Calitz <[email protected]> wrote: > > 2009/8/20 David Glick <[email protected]> > > > > > > > > > > > > > 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 > > > > This is something I'd also love to see happen. It would really make life > so > > much simpler in the long run. > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
