I'm currently working on bug 585 - "wine installation process should install and configure wine applications". The first part of the work is done - wine applications, like regedit are installed by Wine build process.
I wanted to ask you about correct approach to place these applications to deploy them.
I think that applications can be called with full path, with or without extention, names in different cases. So I'm going to change wineinstall process to create symbolic links in c:/windows/system32 e.g. for regedit:
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? Regedit can be called as REGEDIT, RegEdit, Regedit, regedit. Now multiply this on number of extentions exe, EXE. This is without considering really fancy cases, like "ReGeDiT".
Is there a way to handle this problem?
Thanks, Andriy Palamarchuk
__________________________________________________ Do You Yahoo!? Yahoo! Health - your guide to health and wellness http://health.yahoo.com
Andriy Palamarchuk apa3a@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
The .exe variant should be enough. Wine will append .exe if there's no extension.
This fixes problems with full path and with using or not using file extention, but how to handle case-insensitivity? Regedit can be called as REGEDIT, RegEdit, Regedit, regedit. Now multiply this on number of extentions exe, EXE. This is without considering really fancy cases, like "ReGeDiT".
This is already handled by the filesystem functions. You don't need to do anything.
--- Alexandre Julliard julliard@winehq.com a écrit : > Andriy Palamarchuk apa3a@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
On Thu, May 02, 2002 at 12:17:32PM -0700, Andriy Palamarchuk wrote:
I'm currently working on bug 585 - "wine installation process should install and configure wine applications". The first part of the work is done - wine applications, like regedit are installed by Wine build process.
I wanted to ask you about correct approach to place these applications to deploy them.
I think that applications can be called with full path, with or without extention, names in different cases. So I'm going to change wineinstall process to create symbolic links in c:/windows/system32 e.g. for regedit:
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? Regedit can be called as REGEDIT, RegEdit, Regedit, regedit. Now multiply this on number of extentions exe, EXE. This is without considering really fancy cases, like "ReGeDiT".
Is there a way to handle this problem?
Eh ? I thought "Filesystem" = "win95" handled this nicely ? Unless I misunderstood something completely fundamentally fatally...