Re: Re: dist_plone script in cvs
"Alexander Limi" <limi-z4DKO/[email protected]>
| Newsgroups | gmane.comp.web.zope.plone.installers |
|---|---|
| Organization | Plone Solutions · http://www.plonesolutions.com |
| Message-ID | <opr40jx9uovhba00@serafin> |
On Wed, 17 Mar 2004 09:38:20 +0100, Simon Eisenmann <simon-4x/[email protected]> wrote: > Alexander Limi wrote: >> 3) Adds the cross-platform additions that consitute Plone, and creates >> Plone-X.Y >> The installers are normally built on top of [3]. Plone Core[2] is for >> people who just want the minimal Plone install with minimal >> dependencies, aka. People Who Know What They Want. > > Well .. i dont really see a reason why there should be a tarball of a > platfom specific plone. Please explain :) This is the "source install" if you like. Not platform-specific, but includes the extra elements that are not in Plone Core (which is the minimal install, with only Plone + dependencies). > I would rather see it like this >> Which means any platform-specific installers: > > a, get the dist_plone script > b, run it with python2.3 dist_plone.py --target=$PLATFORM > c, have all required software ready to use in the destination dir > and build the installer from it (best from another script) > > Of course the script could also roll out tarballs like > Plone.$PLATFORM.tar.gz > with the following structure: > - download (contains all the downloaded archives) > - lib/python (contains all required python modules) > - lib/pyhton/Products (contains all Product) Just to clarify (I believe we agree, but just to make sure :): "Plone" (Plone-X.Y.tar.gz) should just be a tarball with all the things you stick in the Products directory, and used as a base for the other packages. > The core tarball will build only with products so there is no folder > stucture there and it wont contain the downloaded archives as well. We need both "Plone Core" (audience: minimal install) and "Plone" (audience: those who want the full Plone, but can't/won't use the installers) available. What happens in the Platform-specific packages is up to the authors, as long as they build on "Plone", and add whatever they think is suitable. All of these add-ons should be in uninstalled form, however. Optionally they can build a plone-core RPM/DEB if they want the minimal install to be available too. > In all tarballs will be a file CONTENTS.txt containing a list of the > urls which have been downloaded an when. Sounds good. -- __________________________________________________________________ Alexander Limi · Interaction Architect · Plone Solutions Development · Training · Support · http://www.plonesolutions.com __________________________________________________________________ Plone Co-Founder · http://plone.org · Connecting Content ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70&alloc_id638&op=click