Re: Plone 3.0.2 bundle for openSUSE
rmiddleton <[email protected]>
| Newsgroups | gmane.comp.web.zope.plone.installers |
|---|---|
| Message-ID | <[email protected]> |
I tried the YAST install. "nothing provides python24-imaging needed by plone-3.1.3-1.1.i586" YAST cannot find python24-imaging in available packages. It does seem to find everything else. Also did not find it in an OpenSUSE software seach. Randy markone wrote: > > > Markus Tesmer wrote: >> >> Hi, >> ... >> - which has the >> following advantages for us: >> >> - Plone packages are built for several SUSE releases: >> >> http://download.opensuse.org/repositories/home:/tesmer/ >> > I just looked at this yesterday, preparatory to a trial install of Plone > and noticed that the build for openSUSE was not for either of the two > latest releases, 11.1 or 11.2. > > Now I understand the 11.2 aspect, as that will still have been at the rc > stage when you uploaded the package, but missing 11.1 seems like an > oversight. > > > >> - Instead of distributing a large bundle all required files are provided >> as an >> additional installation source by the Build Service. Thus the >> installation >> prodecure can be done using the usual system administration frontend. >> > > Raises another question, I am afraid: My 11.1 install has a later python > than comes with the standard 'unified installer' version. Does the SuSE > Build System version install its own python (ie, the older 2.4 version) or > does it use the newer 2.6 version, that I already have installed (always > assuming that the 3.0 version is not workable without serious work, like > running the conversion script and maybe ending up in 'untested territory' > which is somewhere I'd rather not be). > > > >> - The installation will be much easier using the One Click Install >> feature. It >> suffices to visit one URL with the browser to trigger the automatical >> installation: >> > > Yes and no (sort of). I am very glad that you are doing this and I > appreciate your effort, but the results with one click install can be a > bit questionable, if this is used for multiple packages (it can make a > mess of repos and their priorities, but there is an easy work-around). > > I use one click to trace down the package and its repo and manually add > the repo at a low priority level (a high number) and install through the > standard 'Yast' > 'Install and Remove Software', as I find that more > reliable. > > So, everything that you have done is still useful, it is just that the > install is a teensy bit more involved. (Alternatively, you can let 'one > click' do what it wants with your repos, and sort it out later, but, if > you let one click at your repos several times before you sort it out, that > is going to be more effort, honest.) > > > >> At the moment we provide voluminous installer packages that contain >> everything >> people need to get Plone up and running. In addition we could provide a >> page >> describing the much easier One Click Install way. What do you think about >> it? >> To answer one obvious question: download statistics for the openSUSE >> Build >> Service shall be made available in future. >> > > No, good idea, undoubtedly. And, you can get yast to do sensible things > with dependencies so that, eg, python, etc, are only downloaded if > necessary, that is only sensible. > > > > > -- View this message in context: http://n2.nabble.com/Plone-3-0-2-bundle-for-openSUSE-tp362345p4164792.html Sent from the Installers mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev