|
From: John P. <jo...@jo...> - 2005-07-18 04:28:11
|
On Sun, Jul 17, 2005 at 11:32:00AM -0300, Gabriel Gazzán wrote: > I agree. > > El Domingo 17 de Julio de 2005 05:05, Mark K. Kim escribió: > > No, don't close it yet... The installer needs to be modified to check > > whether it's being installed as an admin, then provide an option to > > install for all users along with an option to install for a single user. > > It's a hassle for an admin to install programs like Tux Paint for all > > users without the option to install for all users. > > > > If the directory or registry permissions are incorrectly set, that's a > > bigger problem that the admin should fix. That's not a problem that an > > installer should deal with any more than it is for an installer to do a > > disk integrity check before installation. Let's leave those for the admin > > and the fix-it tools to deal with, and make the Tux Paint Installer > > provide the installation options that other tools cannot be used to > > provide. > > > > My late-night 2 cents. > > > > -Mark > Hi, sorry for not chipping in earlier, been busy. I agree also. We've been aware of various defects in the installer for a while. I recently had cause to get into installer building again and, after trying for a while, gave up on NSIS. Take a look at InnoSetup http://www.jrsoftware.org/isinfo.php I've used it in the past but gave up because it wasn't customisable. Now it supports PASCAL scripting and has relevant features built-in that have to be cobbled together for NSIS. I believe it is suitable for use in projects such as Tux Paint, licence-wise. Terminology: 'privileged' - administrator or poweruser 'all users' (if privileged) - shared install defaults 'privileged current user' - }- private install defaults 'restricted current user' - My summary of the suggestions so far (for Win32 build): - change the default location of the settings and personal stamps, fonts etc. to something per-user. e.g. "%HOMEPATH%\Application Data\TuxPaint" - change the default location of the images/thumbs to something per-user. e.g. "%HOMEPATH%\My Documents\My Pictures\TuxPaint" - change installer to recognise privileges and offer 'all users' install. Otherwise, install in some user-specific place, with user-specific registry entries etc. - change stamps and font installers to recognise privileges and try and find Tux Paint using relevant registry entries. Can also offer 'all users' and install in the same directory as Tux Paint (like now). Otherwise, install in the above settings directory. - if installing as a privileged user, prevent execution of tuxpaint-config by restricted users. - optionally run tuxpaint-config as current user after completing installation. - provide more information on building Tux Paint and dependencies on Windows using MINGW/MSYS. In the (default if privileged) 'all users' scenario, the default install location would be "%SystemDrive%\Program Files\TuxPaint". Otherwise, it could be "%HOMEPATH%\Programs\TuxPaint". One thing I've not tackled is the issue of restricted users being able to, for example, switch printing on even if the global settings disable it. If it is possible for Tux Paint to know if it is being run by a restricted user (maybe test write permissions on the global settings file?), it would be possible to ignore/disable certain command-line options and local settings. Maybe this is already in hand? Comments? Have I missed anything? cheers, John Popplewell. PS I might even have time to do some this week, but time for bed now :-) |
