Wine devel packages ready for testing

Michael Müller michael at
Mon Nov 30 13:27:09 CST 2015

Am 30.11.2015 um 03:21 schrieb Austin English:
> I'm not sure where you plan on installing wine on OS X, but be aware
> that 10.11/El Capitan forbids installing into /usr (except
> /usr/local):
> I ran into that recently in my day job.

Currently we install wine staging into /opt/wine-staging which seems to
work. I would prefer to install the new packages into the home
directory, so that also users without admin rights can install the
package. The only problem are the dependencies since they usually do not
use relative rpaths and they might contain the prefix embedded in the
executables. Not sure if this is a problem, I need to test this.

> You may also want to consider getting an Apple Developer Key so that 
> packages can be signed and users can avoid scary warnings, but I don't
> know if that would work in your cross-compile setup.

It is indeed difficult to sign executables without using any proprietary
tools by Apple, but it seems like I found one which works. "codesign -vd
wine" seems to like my signature, except that the tool slightly messed
up the timestamp of the signature which now lies before the creation
date of my self signed certificate. I am sure this can be fixed though
;-). Signing the whole package is most probably a bit more difficult
than just signing one executable, but I am sure this is doable.

I guess it is necessary to pay 99$/year for the developer program to get
your key signed, right?

More information about the wine-devel mailing list