Winelib apps and PATH

2002-05-14 Thread Sylvain Petreolle
Hi, Testing wine's control.exe replacements makes me show this : If i remove/rename original control.exe, I can do : $ control and I have the Wine Control Panel as it has been installed in /usr/local/bin. But I cannot do: $ wine control wine: cannot find 'control' So if one app calls for

Re: Winelib apps and PATH

2002-05-14 Thread Joerg Mayer
On Tue, May 14, 2002 at 09:44:07PM +0200, Sylvain Petreolle wrote: Shouldn't we provide a default drive for /usr or /usrlocal/bin in the config file ? This would solve the can't load winedbg 123456 issue that users usually include in their first reports. (the debugger cannot be launched

Re: Winelib apps and PATH

2002-05-14 Thread Alexandre Julliard
Joerg Mayer [EMAIL PROTECTED] writes: While I think that doing something like this should really be done, I don't like mixing windows/wine executables and linux (aka native os) executables. Maybe some directory like /usr/local/win (or winebin) would be better. My plan is to integrate that

Re: Winelib apps and PATH

2002-05-14 Thread Sylvain Petreolle
You have exactly the same idea I had 3 months ago, but at this moment I thought this wouldn't be accepted. And this is so simple to desactivate a builtin app this way when it's not enough complete. My plan is to integrate that with the loadorder and builtin dll mechanism. So