Re: [Plone-developers] Proposal: buildout-based Plone Installer for Windows (PLIP #227)

Hi Tarek,

On Fri, Mar 14, 2008 at 2:50 PM, Tarek Ziade <[email protected]> wrote:
> 1/ The pre-built story:
>
> I am wondering if we really need to ship prebuilt versions.. If I recall it
> correctly,
> a plain Plone doesn't need extra libs to be compiled, just a compiler.

But why would you compile everything on the target system? There's no
reason for that at all, it's just wasting resources.

> And Mingw can be shipped with the installer, without having to be installed
> on the system
> itself. It is just a simple folder that can be linked to distutils.

That can be done yes.

> 2/ the buildout
>
> I think we could come up with a buildout that knows how to build an
> installer in different
>  flavors, and we need to clearly specify in the PEP what each one contains:
>
> - non-dev:
>     - all needed to run a plone : zope, plone, pywin32, PIL and its dlls
> (libjpeg.dll, etc)
>     - extra elements: ZopeSkel <- neat idea !
>      - (maybe mingw32)
>
> - dev:
>   - all non-dev
>   - mingw32, hooked to python
>   - the subversion client
>   - a set of developers tools: tail, (vim), tar, etc  <- these are important
> imho because it let people follow all
>      tutorials that are not specifying that some commands are only under
> linux, so they often waste some time
>     to get those small tools running. Maybe msys ?

GNU utilities for Win32 as Yves pointed out.

> For me, dev should definitly lead to something similar that what Linux
> provides in any cases.
>
> I have dropped our buildout that makes the zip file in the collective here:
>
> http://svn.plone.org/svn/collective/win32binaries
>
> It is composed of a install.bat file that runs the steps, and of a list of
> installers that
>  are fetched. I guess the InnoSetup recipe could work the same way, rather
> than
> working itself on a zip file produced by win32binaries.

Great! That will be very useful.

> 3/ uninstalling
>
> I also would be in favor of a unified uninstaller that knows how to remove
> all third-party softwares.
>
> In any case, thanks for working on this Sidnei !

One thing that I noticed is that your recipe installs things
system-wide. That's not required at all. We have internal scripts at
Enfold that build a self-contained Python+PyWin32 package that doesn't
need to be installed system-wide.

-- 
Sidnei da Silva
Enfold Systems http://enfoldsystems.com
Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214

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