Uwe Stöhr wrote:
It's not the installer's business to enforce such policies.
The current installer runs without admin priviliges; so should yours.
I tried it but there were too many problems to cover all specialities of
the third-party programs. If the user has admin privileges I can assure
that it works on every Win2k and WinXP-installation.
And also when the user uses your installer he needs admin privileges to
install for example the latest Perl.
* LyX 1.4 won't need Perl.
* I see heaps of complaints to the Python devs about Python 2.4 requiring
admin priviliges. Python 2.3 and below don't.
* MSYS doesn't need admin priviliges.
* You say ImageMagick does, but ImageMagick isn't *required* to run LyX.
* There are certainly latex distributions out there that don't require
admin priviliges. Again, you don't *need* latex installed to run LyX.
It's perfectly reasonable to tell your user that some parts of the
installation procedure need admin rights, for reasons outside of your
control. If the installer is run by a non-admin then restrict what gets
installed or enable the installer to upgrade itself to admin priviliges for
those bits (presumably requires a password dialog).
And what if other installers will
need admin privileges too in future releases?
That's their problem. It's not something you should be concerned about.
Angus
