[prev in list] [next in list] [prev in thread] [next in thread]
List: bacula-bugs
Subject: [Bacula-bugs] [bacula 0001721]: Incorrect default installation path
From: Mantis Bug Tracker <nobody () baculabugs ! unixathome ! org>
Date: 2011-04-09 2:05:18
Message-ID: 1b6e40a5f3edb80e3aa3e8eb5ca95dc6 () bugs ! bacula ! org
[Download RAW message or body]
The following issue has been CLOSED
======================================================================
http://bugs.bacula.org/view.php?id=1721
======================================================================
Reported By: max
Assigned To:
======================================================================
Project: bacula
Issue ID: 1721
Category: Win32 File Daemon (client)
Reproducibility: always
Severity: minor
Priority: normal
Status: closed
Resolution: won't fix
Fixed in Version:
======================================================================
Date Submitted: 2011-04-08 10:06 GMT
Last Modified: 2011-04-09 02:05 GMT
======================================================================
Summary: Incorrect default installation path for Windows
client
Description:
The Nullsoft installer always selects "C:\Program Files\Bacula" as the default
installation path without regard to the PROGRAMFILES environment variable, which
may be set to something else.
The installer should be updated to use "%PROGRAMFILES%\Bacula" as the default
installation directory.
======================================================================
----------------------------------------------------------------------
(0005827) kern (administrator) - 2011-04-08 11:09
http://bugs.bacula.org/view.php?id=1721#c5827
----------------------------------------------------------------------
We have tried various "standard" installation schemes in the past, and they all
without exception have problems, particular with foreign language computers and
particularly ones that have accents in their paths. It is a nightmare.
We won't change it.
If you would like to change it, you can either try to modify and build from the
source yourself or try to move the files later.
----------------------------------------------------------------------
(0005829) max (reporter) - 2011-04-08 11:22
http://bugs.bacula.org/view.php?id=1721#c5829
----------------------------------------------------------------------
Thanks for the info. The problem appears to be with the Nullsoft installer not
supporting Unicode:
http://en.wikipedia.org/wiki/Nullsoft_Scriptable_Install_System#Unicode_support
Perhaps it would be worthwhile to switch to another installation system that has
proper Unicode support, and at the same time release the client as a .msi
package, which could be deployed via Group Policy?
I'm currently trying to decide how to push the client to a few dozen computers
at work. The best solution right now seems to be to extract all the files and
repackage them because of several problems with the official installation. My
current list is:
1. Not msi, so can't be deployed via GP.
2. Installs the files to the wrong location in our environment.
3. The /S flag is not honored for the uninstall, so using some 3rd party tools
like WPKG is also not a perfect solution.
4. I need some way of communicating client names and passwords back to the
director, this will likely require some custom scripting.
Basically, I think there is some room for improvement in the client
installation. It works fine for small environments, but it becomes a bit of a
pain to deploy and later update on many computers.
----------------------------------------------------------------------
(0005830) kern (administrator) - 2011-04-09 02:05
http://bugs.bacula.org/view.php?id=1721#c5830
----------------------------------------------------------------------
Thanks for the information. We had not fully researched where the problem was
but applied a solution that is guaranteed to work.
Yes, we realize that there are distribution problems with .exe's. The problem
with switching to another installer package is that we build *everything* from
A-Z on Linux with a single "make" command using cross-compilers. We haven't
extensively researched if there are open source installers that will handle
Unicode and create .msi files, but if there are, we would still need to
"convert" the installer to compiling on Linux machines, which is a fair amount
of work that for the moment is not a high priority.
If some open source programmer wants to find a suitable .msi installer and build
it in our Linux cross-compile setup, we would be happy to receive a contribution
and switch. Otherwise, we will get to this problem at some point when it
becomes a bit more critical, when I cannot say.
Issue History
Date Modified Username Field Change
======================================================================
2011-04-08 10:06 max New Issue
2011-04-08 11:09 kern Note Added: 0005827
2011-04-08 11:09 kern Status new => closed
2011-04-08 11:09 kern Resolution open => won't fix
2011-04-08 11:22 max Note Added: 0005829
2011-04-08 11:22 max Status closed => feedback
2011-04-08 11:22 max Resolution won't fix => reopened
2011-04-09 02:05 kern Note Added: 0005830
2011-04-09 02:05 kern Status feedback => closed
2011-04-09 02:05 kern Resolution reopened => won't fix
======================================================================
------------------------------------------------------------------------------
Xperia(TM) PLAY
It's a major breakthrough. An authentic gaming
smartphone on the nation's most reliable network.
And it wants your games.
http://p.sf.net/sfu/verizon-sfdev
_______________________________________________
Bacula-bugs mailing list
Bacula-bugs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-bugs
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic