Thanks for your answers. I have a few more question :
1) How the python2.4.5 (installed by UnifiedInstaller) is update (not by buildout I presume) ? 2) I had the following problem with the last buildout (installed by the UnifiedInstaller 3.1.7) : I get my development packages (in src) by an svn checkout and I was forced to remove the .svn directory at the root of my packages (eg src/ns.myProduct/.svn) 3) In case of problem, is it possible to generate the same installation with the already downloaded packages ? If so, how ? If I re-run a particular UnifiedInstaller several month later after my initial installation, I won't get exactly the same configuration ? That could be a problem for a production server ? 4) The buildout.cfg generated by the UnifiedInstaller has an option "newer=false" that mean that existing packages will not be updated (unless I make a ./bin/buildout -n ?) Thanks again -- View this message in context: http://n2.nabble.com/Which-installer-for-Plone-tp1515213p1520145.html Sent from the Installation, Setup, Upgrades mailing list archive at Nabble.com. _______________________________________________ Setup mailing list [email protected] http://lists.plone.org/mailman/listinfo/setup
