Vincent Béron vberon@mecano.gme.usherb.ca writes:
Alexandre, what are the guidelines for installing winelib applications in /foo/bin/?
It should be restricted to apps that users will frequently run from the command-line on Windows so that they expect the same behavior on Wine, or else to apps prefixed with 'wine' as there isn't a risk of conflict in that case. I'm not sure msiexec qualifies; is it really something that end users are expected to use on Windows?
Le ven 23/07/2004 à 13:54, Alexandre Julliard a écrit :
Vincent Béron vberon@mecano.gme.usherb.ca writes:
Alexandre, what are the guidelines for installing winelib applications in /foo/bin/?
It should be restricted to apps that users will frequently run from the command-line on Windows so that they expect the same behavior on Wine, or else to apps prefixed with 'wine' as there isn't a risk of conflict in that case. I'm not sure msiexec qualifies; is it really something that end users are expected to use on Windows?
Does double-clicking on a .msi package (and thus run msiexec) applies?
I don't think many users actually go to a command prompt and exec msiexec that way. The native version gives its error messages via MessageBox, so it looks like its a gui app more than a cli app.
Vincent
Vincent Béron vberon@mecano.gme.usherb.ca writes:
Does double-clicking on a .msi package (and thus run msiexec) applies?
No, if the user doesn't have to type it then we don't need the binary in /usr/bin, it can always be launched with 'wine msiexec' anyway, so we can put that in the association for .msi files.
-
Alexandre Julliard -
Vincent Béron