Re: Unified Installer with Buildout

Hi Steve.

The idea of a UnifiedInstallerBuildout is great ;)

I have a question: I've installed a zeo cluster using

https://launchpad.net/plone/3.0/3.0.4/+download/Plone-3.0.4-UnifiedInstallerBuildout-a2.tar.gz 

and changed the http ports for the instances in buildout.cfg but when I run
./zeocluster/bin/buildout e get this warning:

Couldn't find index page for 'plone.recipe.unifiedinstaller' (maybe
misspelled?)

Do you know what might be?

best regards,
Rui




Steve McMahon wrote:
> 
> An experimental version of the Unified Installer Plus Buildout is 
> available for testing at:
> 
> https://launchpad.net/plone/3.0/3.0.4/+download/Plone-3.0.4-UnifiedInstallerBuildout-a1.tar.gz
> 
> This is an approximately 32 MB download.
> 
> Please file narrow bug report and feature requests to 
> dev.plone.org/plone, marking the component as "Installer (Unified)" and 
> specifying the UI+Buildout.
> 
> More general discussion, including evaluations of the concept and 
> implementation, can be on the list, or as comments to PLIP #209 
> <http://plone.org/products/plone/roadmap/209>.
> 
> Motivation for doing this:
> 
> The big hurdle that the Unified Installer gets many users over is the 
> building of a Python -- complete with PIL, libjpeg, and libz interfaces 
> -- that will work with Zope and Python. However, users with Unified 
> Installer builds face a problem when it comes to adding egg-based 
> products as they won't have the easy facilities for adding eggs and zcml 
> provided by buildout. Also, minor-version migration is painful for 
> Unified Installer users. They must install the new update and copy over 
> their data and custom packages. In a buildout environment, they'd be 
> able to just run bin/buildout.
> 
> 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.
> 
> I look forward to your feedback and collaboration!
> 
> Steve
> 
> 
> -- 
> ______________________________________________________
> 
> Steve McMahon
> Reid-McMahon, LLC
> steve-HR5nRXif9uVv8oa/[email protected]
> [email protected]
> 
> -------------------------------------------------------------------------
> 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
> _______________________________________________
> Plone-installers mailing list
> Plone-installers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/plone-installers
> 
> 

-- 
View this message in context: http://www.nabble.com/Unified-Installer-with-Buildout-tp14264934s21260p14526997.html
Sent from the Installers mailing list archive at Nabble.com.


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/