On Jan 7, 2013, at 9:15 AM, Ken Thomases wrote: > On Jan 7, 2013, at 1:23 AM, Per Johansson wrote: > >> On Mon, Jan 7, 2013 at 4:48 AM, Charles Davis <cdavi...@gmail.com> wrote: >>> >>> With this, you won't be able to launch Wine from the Finder or with open(1) >>> prior to 10.6. >> >> I don't see how you'd do use open or the Finder to launch wine, could >> you explain more detailed? > > Yeah, I'm not sure it's a real problem, It won't be--I don't imagine anyone would want to double-click on the Wine executable, and they certainly wouldn't use open(1) when they could just run wine(1) directly--unless Wine grows support for file associations on the Mac. Then, when some poor user stuck on Leopard double-clicks on a file, expecting it to open up with Wine, it'll fail, because Wine declared to LaunchServices that it can't run on Leopard. I might be mistaken, since we'd probably end up just emitting app bundles with shell scripts that exec wine(1) directly, where LS wouldn't be involved in launching Wine itself. One area that might still be a problem, though, is if we associate *.exe files with Wine itself: then when a user double-clicks on a Win32 executable, LS will go straight to executing Wine. Don't know if that's possible with embedded Info.plist files, though.
Chip > but that key should probably not be there anyway. I'll resubmit with that > removed. > > Thanks for reviewing. > > Cheers, > Ken >
