Re: Unified Installer with Buildout

Steve McMahon wrote:

> Current implementation:
> 
> This test version includes all the eggs and downloadables required for 
> Plone 3.0.4 so that it will run off-line. (A version that would pick 
> them up online could be as small as 11MB.)
> 
> The initial build phase is the same as the Unified Installer: it builds 
> Python 2.4.4 and PIL (and, optionally, libz and libjpeg) and creates a 
> plone user if run as root. ZopeSkel and all its dependencies are also built.
> 
> In the next phase, a buildout template (different for zeo and 
> standalone) is copied into place along with the egg/download cache. 
> "buildout -No" is then run to finish up.
> 
> Some of the cleanup work that used to be done with shell scripts is now 
> done with a plone.recipe.unifiedinstaller recipe (included as an egg; 
> this is not yet on PyPI). plone.recipe.command is used to set ownership 
> for root installs.

Why do we need this recipe? Is it just for creating start/stop control 
scripts? If so, that's probably fine, though the more we can generalise 
the better.

I also wonder why buildout.cfg puts things in 
${install_root}/.buildout/eggs. That seems a bit obfuscated. Why not 
just leave the defaults (${buildout}/eggs)? Or, if you want a shared 
directory, just have something like ${install_root}/caches/eggs and 
similarly for downloads.

Really, it'd be best if you didn't have this option at all, though, 
since then people with a ~/.buildout/default.cfg would have those 
settings count.

All in all, it looks really good though!

Martin

-- 
Author of `Professional Plone Development`, a book for developers who
want to work with Plone. See http://martinaspeli.net/plone-book


-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php