Silvio <[email protected]> writes: > I forgot to specify the cfg file here (as I don't usually do) and it > didn't work. So I added a buildout.cfg that loads 316.cfg to be used > as a default for the latest supported version.
The "buildout.cfg" used to be the one for Plone 2.5.5, which was never the version I wanted, and I got tired of ruining my buildout every time that I forgot and re-ran "buildout" without any arguments. :-) 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. However, I happily encourage *local* symlinks that we each make from "buildout.cfg" to the version we're currently working on. Anyway, that's just my vote. :-) I know that's not how things have been working in trunk, so I'd assumed that this change would disappear once my branch is merged then destroyed. -- Brandon Craig Rhodes [email protected] http://rhodesmill.org/brandon --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
