Re: Unified Installer with Buildout

On 12/10/07, Martin Aspeli <[email protected]> wrote:
> >...
> > 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.

What this really takes on is the task of making the result look as
much as possible like that of the old Unified Installer -- and be as
easy to use. So, it writes out a little instruction sheet to
adminPassword.txt and creates start/stop/status/restart scripts like
the previous UI. I suspect that the folks doing binary installers may
end up with a similar (but specialized) recipe.


> 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.

I did want a shared directory, as folks may run this lots of times.
And, I wanted it to be in the target directory (rather than a
~/.buildout) to deal with the root-install case.

"caches" or "buildout_cache" would probably be better than
".buildout". No reason to hide it.

> 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.

Someone who can manage a split buildout with a ~/.buildout/default.cfg
is probably not the typical user for the Unified Installer. And, for
the production install use case, I think we really want all the parts
in the target directory, and not in anyone's home directory. This is,
of course, all very much open for discussion!


> All in all, it looks really good though!

Thanks!

>
> 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
> _______________________________________________
> 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