I don't have any use for the debug info at the moment, and about Python
bindings: It might actually be a better idea to have a seperate installer
for the Python bindings (as they probably need to be installed in
Python-specific locations etc, and perhaps even be created using the Python
dist-utils)
So I guess that actually, I have no need for any changes to the installer.
--Tim
-----Original Message-----
From: Jostein Christoffer Andersen [mailto:jostein@josander.net]
Sent: vrijdag 11 juli 2003 10:49
To: Leeuw van der, Tim
Cc: dev@subversion.tigris.org
Subject: Re: Vacation - Can someone roll the win32 setup?
On Friday 11 July 2003 09.31, Leeuw van der, Tim wrote:
> What other software is required, in general? Open-source, or
> commercial? I understand that the compiled binaries are already done,
> so that the person rolling the installer doesn't need MSVC.
You need this packages which is mentioned in the file
packages/win32-innosetup/Readme.txt: Inno Setup, ISTool, 7-zip, Perl,
Packages for converting XML documentation and MS HTML Help Workshop.
The file have all the links you need in order to download the packages.
All of them are free/freeware and most of them are Open Source
(exception is HTML Help Workshop). It's important that all the Inno
Setup related packages are in the 3.x series (the 4.x's which is beta
are not stable enough).
> What about Python-bindings? Will they be included in the
> installer-builds, or is that not desirable in your opinion?
No (not this time at least), here is some reasons/thoughts/workarounds:
* I'm using 7-zip for compression of the setup but the Python-bindings
are still making the setup approx. 1.6 MB bigger.
* Do an "ordinary" user need the bindings? Which users are the
installer's target?
* The bindings can be downloaded from the subversion site.
On the other hand: -Maybe I should reconsider all of it because (?):
* The installers audience are developers and sysadmins (?).
* The "real end users" will use Tortoisesvn and other GUI solutions.
* Many developer related files are already included in the setup,
such as the Berkeley header files.
Maybe The Windows Installer should be targeted for developers and
sysadmins and maybe I should not fear a bigger size of the installer so
much. Then I should include the debug info as well as the Python
bindings as well.
Tortoisesvn are already doing a fantastic job for end users and RapidSVN
are getting better and better. And the line of misc. end user related
Subversion projects are getting longer and longer :-).
This is what I'm working with now (I will not finish it before after my
vacation):
* Misc. downloads of missing system file during/after installation.
* Detection/stop/start of apache service during installation.
I think that the "typical" installer setup should focus on just getting
the Subversion Revision Control installed. But maybe it should include
Python bindings, debug symbols and other stuff that fits to a package.
Any thoughs anyone?
Jostein
--
Jostein Chr. Andersen <jostein_at_josander.net> http://www.josander.net/
Public PGP Key:
Key: http://www.josander.net/pub_keys/jostein_josander.net.asc
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Jul 11 11:16:27 2003