>> > My vote would be against a default "buildout.cfg" in Subversion if we're >> > going to support multiple versions of Plone; it just makes it too >> > dangerous, in my opinion, for people working on some other version. If >> > you run "buildout" without choosing a version, that error message is >> > necessary to remind you that the choice must be made. >>
Extending buildout is much better way than having a default buildout for each version. buildourt.cfg might be different depending on installer and OS - we do not want to support that variation. If you want to see the heacache check out buildout.cfg in Windows installer. Instead we could provide different extension for each Plone version if version soup is a problem. I suggest we use combination of extends and [versions] to deal with versioning problems. E.g. [buildout] extends = http://dist.plone.org/release/3.3/versions.cfg http://svn.plone.org/svn/collective/getpaid.buildout/getpaid_for_3.3.cfg getpaid_for_3.3.cfg contains [versions] Products.PloneGetPaid=0.8 getpaid.somepackage=0.7 ... vs. [buildout] extends = http://dist.plone.org/release/4.0/versions.cfg http://svn.plone.org/svn/collective/getpaid.buildout/getpaid_for_4.0.cfg -Mikko --~--~---------~--~----~------------~-------~--~----~ GetPaid for Plone: http://www.plonegetpaid.com (overview info) | http://code.google.com/p/getpaid (code and issue tracker) 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?hl=en -~----------~----~----~----~------~----~------~--~---
