Correct approach to deploy Wine applications

[Sylvain Petreolle]

 --- Alexandre Julliard <julliard at winehq.com> a écrit
: > Andriy Palamarchuk <apa3a at yahoo.com> writes:
> 
> > regedit -> /usr/local/bin/wine
> > regedit.so -> /usr/local/bin/regedit.so
> > regedit.exe -> /usr/local/bin/wine
> > regedit.exe.so -> /usr/local/bin/regedit.so
> 
> > This fixes problems with full path and with using
> or
> > not using file extention, but how to handle
> > case-insensitivity?

Case-insensitivity is handled by the filesystem for
now.
> 
> The .exe variant should be enough. Wine will append
> .exe if there's no
> extension.

But the .exe variant is not enough.
You must have tbe .so in your path in order to be able
to execute it.
we could create, as it is done for dlls,  a
"C:\windows\programs" directory containing all the
applications symlinks/binaries.

Another approach is to define in a file what program
should be used natively or replaced by wine's one.

Comments ?

___________________________________________________________
Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français !
Yahoo! Mail : http://fr.mail.yahoo.com