directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefan Seelmann <seelm...@apache.org>
Subject Re: [Studio] [Apache DS] Windows Installer problems (was Re: [Studio] German translation needed for Studio's internationalized Windows Installer)
Date Thu, 09 Apr 2009 10:26:10 GMT
Pierre-Arnaud Marcelot schrieb:
 > Then, I used another solution and that's what's using the current
> installer. It's using a journal that logs every file that been installed.
> 
> When uninstalling, the uninstaller reads this journal and for any file
> that is in the install directory but not in the journal, it asks you
> whether or not the file or directory should be deleted.
> 
> This may seem good but this leads to several problems:
> 
>     * if the directory you installed the software in is crowded of many
>       other files, you will be asked a lot of questions.
>     * when studio launches, it usually unpack a few plugins in
>       /configuration and as these files were not there at the
>       installation, when uninstalling, you'll be asked a lot of questions. 
> 
> So, this solution is not adeaquate too...
> 

Sorry, if I encouraged you to try this solution. I haven't considered
these /configuration files.

> At the end, I'm considering providing the win32 distribution as a simple
> ZIP file (like Eclipse) but I like the idea of having an installer
> (Windows is a dummies world).

Yes, that's one option.

> The last solution we were considering with Stefan on IM, was removing
> the journal as it's not at a good solution for our particular need, and
> in the uninstaller only remove files and directories we installed
> (without asking if new files have been put in them).
> For example, for Studio, this means removing:
> 
>     * Apache Directory Studio.exe (file)
>     * LICENSE.txt (file)
>     * NOTICE.txt (file)
>     * Release Notes.txt (file)
>     * Uninstall.exe (file)
>     * configuration/ (directory)
>     * features/ (directory)
>     * plugins/ (directory)
>

That would be my preferred solution.

> However, this would of course let the container directory ("Apache
> Directory Studio" directory for a classic installation) on the disk. But
> it's way safer than before and not intrusive as is the uninstall journal.

Maybe it is possible to check if the container directory is empty, and
if so delete it.

Kind Regards,
Stefan


Mime
View raw message