Le 28 juil. 2011 à 11:55, Eric Bréhault a écrit : > Hello, > > I do not know about the current buildout version, but buildout -O > option used to be not entirely trustable. > Last time I was in the same situation, I used -N instead and it worked fine. > > Maybe it had been fixed since, but it worths a try. Hi Eric,
I'm talking about the bootstrap.py script, not about the bin/buildout command itself. Gilles > > Eric > > On Thu, Jul 28, 2011 at 10:53 AM, Gilles Lenfant > <[email protected]> wrote: >> Hi, >> >> This is perhaps not the most suited ML for asking such question. I'm in a >> situation where I need to install a Plone in a windows platform that has no >> access to the internet. >> >> I unzip a tarball that has the buildout space, including all eggs, such it >> **could** work with "bin\buildout.exe -nO -c production.cfg", but the >> bootstrap.py always truilies to grab eggs **that are already in >> $BUILDOUT/eggs** from the internet. >> >> The other solution consists in changing all the paths in bin\buildout script >> such it matches the installation path for various eggs. I need to change >> stuffs in parts\buildout\site.py too in various places. Perhaps I'm missing >> something. >> >> Is there an automated way to run the bootstrap.py with no connection to the >> internet ? >> >> Thanks by advance for any hint. >> -- >> Gilles Lenfant >> >> _______________________________________________ >> Product-Developers mailing list >> [email protected] >> https://lists.plone.org/mailman/listinfo/plone-product-developers >> _______________________________________________ Product-Developers mailing list [email protected] https://lists.plone.org/mailman/listinfo/plone-product-developers
