On Mon, Oct 27, 2008 at 2:19 PM, Gert van den Berg <wine-users@xxxxxxxxx> wrote: > On Mon, Oct 27, 2008 at 7:46 PM, dimesio <wineforum-user@xxxxxxxxxx> wrote: >> >> In general, if an app works in Wine, installing and running it would be exactly the same as in Windows: point and click. Wine normally adds Windows apps to the menu when you install them, and creates desktop links if the installer creates Windows shortcuts. It's only when an app doesn't work out-of-the-box with Wine that it can get tricky. >> > Until the occasional regression... > > A bundled Wine version has the advantage that you are certain about > the exact configuration that the program runs on... (Although static > linking seem to be the only real way of distributing binaries without > breakages on different distros... (This might have changed from the > previous time I tried...)) > > Gert > > That's why you could/should do as Google does with Picasa, and distribute a tested version of Wine. Install it as /usr/bin/wine-yourapp/, or /opt/wine-your-app/, etc. You can then use that version without fear of Wine upgrades breaking it, and the user can install Wine in /usr/bin/wine, or /usr/local/bin/wine, etc., for their other applications. -- -Austin
