Re: Offline Installation and version pegging in 3.2

Well, as far as the implementations details of offline caching, that's easy.
You could do the same thing that grokproject does to enable offline
installs.

[buildout]
extends = versions.cfg
versions = versions

versions.cfg is just a copy of the file that is normally at a URL stored
locally in the same directory as the main buildout.cfg file.

I still like to use the "extends = URL" for my Grok-based projects, since
it's easier to see the version of Grok I'm using by reading the URL than
having to look at a separate versions.cfg file. And upgrades to a newer
version is only a 5 second text-edit versions a 20 second text-edit ;). But
if you've got a flakey 'net connection or dist.plone.org is having a bad
day, then it's nice to follow the practice of using a local copy of the
versions.cfg file anyways since that's one fewer single-point of failure.


-- 
View this message in context: http://n2.nabble.com/Offline-Installation-and-version-pegging-in-3.2-tp1353426p1353579.html
Sent from the Installers mailing list archive at Nabble.com.


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/