Offline Installation and version pegging in 3.2

I'm having a bit of a problem reconciling the version-control strategy we're
using for 3.2a with the need for installers to be able to run offline.

At the moment, a buildout for 3.2a would typically contain the lines:

extends = http://dist.plone.org/release/3.2a1/versions.cfg
versions = versions

The problem is that "extends = URL" doesn't work offline; buildout errors
out. (It will work if you're online, but using the -o flag -- which is a bit
counter-intuitive.)

I think we're going to need some mechanism for caching the version data for
the installers. Folks creating their own buildouts could use this or not, as
they please.

Thinking as I type, this could take the form of a recipe (or extension of a
recipe like plone.recipe.unifiedinstaller) that would do something like:

if buildout running in online mode:
    attempt to fetch version info from specified URL
    if successful:
        write out info in a new cache file
    else:
        issue warning
    inject new version info into version
get version info from cache file
inject into versions

Then, the installers would be robust if they're invoked buildout with -o.

Anybody got a better way to do it?

Steve



-- 

Steve McMahon
Reid-McMahon, LLC
steve-HR5nRXif9uVv8oa/[email protected]
[email protected]

-------------------------------------------------------------------------
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=/

_______________________________________________
Plone-installers mailing list
Plone-installers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/plone-installers