Re: Unified Installer with Buildout
"Steve McMahon" <[email protected]>
| Newsgroups | gmane.comp.web.zope.plone.devel,gmane.comp.web.zope.plone.installers |
|---|---|
| Message-ID | <[email protected]> |
Aha! You'd only run into this if the installer was building local copies of libjpeg or libz. I already had them installed globally (from previous builds), so didn't see it. Fix applied, and a new version will be uploaded soon. On 12/10/07, Martin Aspeli <[email protected]> wrote: > 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 really, really great work. Am I right in thinking this takes > care of Linux, Unix and OS X, or do we still need a separate OS X installer? > > I know Sidnei was looking into a Windows version of this too. I think > this'd go a long way towards unifying our installation experience and > making it easier for people to manage egg-based packages. > > I'm just trying it now on my MacBook (ZEO install, non-root). > > Unfortunately, that ended like so: > > ... > /usr/bin/install -c -m 644 ./wrjpgcom.1 > /Users/optilude/Plone-3.0-buildout/Python-2.4.4/man/man1/wrjpgcom.1 > Existing Python discovered at > /Users/optilude/Plone-3.0-buildout/Python-2.4.4; Skipping Python install. > Unpacking buildout cache to /Users/optilude/Plone-3.0-buildout/.buildout > Generating random password ... > ./install.sh: line 473: > /Users/optilude/Plone-3.0-buildout/Python-2.4.4/bin/python: No such file > or directory > Copying ZEO Cluster buildout template > Running buildout > helper_scripts/cluster-mode.sh: bin/buildout: > /Users/optilude/Plone-3.0-buildout/Python-2.4.4/bin/python: bad > interpreter: No such file or directory > Parts of the install are missing. Buildout must have failed. Aborting. > > Sure enough, there's no Python in > /Users/optilude/Plone-3.0-buildout/Python-2.4.4/bin :-/ > > The problem is in install.sh, line 386. It seems to create the directory > first and then test for that. I changed it to: > > if [ -x $PY ] > > which checks for the python binary directly. That's better - compiling > Python now. > > (10 minutes later) > > yup - Plone starting up ;-) > > Cheers, > Martin > > -- > Author of `Professional Plone Development`, a book for developers who > want to work with Plone. See http://martinaspeli.net/plone-book > f > > > ------------------------------------------------------------------------- > 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-developers mailing list > Plone-developers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org > https://lists.sourceforge.net/lists/listinfo/plone-developers > -- ______________________________________________________ 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