2009/10/31 Juan Pablo Giménez <[email protected]>
>
> El vie, 30-10-2009 a las 19:21 -0400, Brandon Craig Rhodes escribió:
> > 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.
>
> +1
Ok, sorry for committing that change without asking: I didn't think the
choice of not having a buildout.cfg was intentional.
I stay however on my point that we should have a sensible default
buildout.cfg that actually extends the buildout for the latest supported
Plone.
Silvio
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
