This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Vista & coreutils (or any other package)


Brian Dessent wrote:

The manifest route is pretty simple, you just create an .xml file, then
refer to it in a resource file, and then windres does the rest.

But in cases like this, we really *don't* want to run with elevated privileges - if I'm "install"ing to /tmp, I definitely don't want to raise my privileges needlessly and potentially set up a security risk somewhere. (Admittedly this is an unlikely scenario, but...)


Also, you want an *unprivileged* user to be able to run install to an unprivileged location, and such a manifest won't help (because that user won't ever be able to raise their privileges without knowing an administrator password).

Perhaps if we did this (cygwin-specific hack) instead?

* Rename "install.exe" to "inst-all.exe" (or something that won't trip Vista's braindamage)
* Supply a one-line "install" shell script to exec inst-all.


* And then, in turn, we could provide an option to "install" to hack other packages' installations of executions named "xxxinstallxxx.exe", etc., to use this subterfuge and create the script and renamed execute on the fly in the install location.

(I.e. when you run

/usr/bin/install [--maybe-some-option] myupdate /usr/bin

"install" would actually copy myupdate.exe to /usr/bin/myup-date.exe, and create a /usr/bin/myupdate shell script to invoke myup-date.)


-- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]