Suggestion: You need two kits.
1) Server kit
This is reasonable to require admin priv and use HKLM
This will need DB4
Probable contains the client kit.
2) Client kit
If you have admin priv then install for all users
Otherwise install for the current user only.
No DB4 required.
The issue with GUI clients and other tools is finding where
SVN is installed. Its then easy to check version info.
Your registry keys do not help me find SVN.EXE or the Swig'ed
wrappers. It's not always possible to rely on tools being on
the PATH.
Maybe you need a convention of placing the location of SVN and
another info, like version in HLKM if you can otherwise in HKCU.
Tools then can search HKCU before HKLM to find the SVN data.
(This would also allow a devo to override the HKLM data to test
a new version without trashing the install.)
Which installer are you using? I have used InstallShield a
lot and do not like it. I'm in the process of migrating to INNO
that is free software and well designed, uses text file to hold
project details. The Windows Installer tools all use binary blobs
for the project details that makes review and auditing near
impossible.
INNO is at http://www.jrsoftware.org/isinfo.php
Barry
> -----Original Message-----
> From: Jostein Christoffer Andersen [mailto:jostein@josander.net]
> Sent: 30 July 2002 08:24
> To: dev@subversion.tigris.org
> Subject: Windows Installer: -Feedback needed please
>
>
> Hi,
>
> I want some input and thoughs about how things should be done with the
> Windows installer, it's not wise to let one person (me) decide how
> things should be done and things can allways be better.
>
> The Subversion project are getting bigger and many third party packages
> are required.
> The Subversion project itself have a new family member (rapidsvn) and
> will probably continue to be bigger.
>
> I have some points that I feel that need feedback and you may have other
> issues to:
>
> * Should Subversion for Windows require Administrative
> privileges (NT versions)? Right now, the installer puts
> the following strings in the registrey:
> HKLM/Software/Tigris.org/Subversion|Revision: "2667"
> HKLM/Software/Tigris.org/Subversion|Version: "0.14.0"
> I have done this for future use (for gui clients etc).
> * Should I exclude the Berkeley DB from the installer?
> It is possible to download it from within the installer
> while installing Subversion for Windows. In that case,
> it may be good to make a Windows installer for Berkeley.
> * What about offering the person who are installing
> subversion to download a rapidsvn package during
> the installation (when it's ready)?
>
> If we are offering the users to download packages during the
> installation, then the Berkeley package (and others) must be aviable
> with other filenames, making sure that the latest versions are aviable
> for the installer.
> This should be possible by symlinking the packages to db-latest.zip,
> rapidsvn-latest.exe on a FTP server
> The installer can fetch files via HTTP and FTP.
>
> Any comments are welcome.
>
> Thanks
>
> Jostein
>
> --
>
>
> ----------------------------------------------------------------------
> Jostein Christoffer Andersen <jostein@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
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jul 30 13:05:16 2002