conflict with macports
Adam Dershowitz Ph.D., P.E.
dersh at alum.mit.edu
Wed Jun 11 05:59:52 PDT 2014
On Jun 11, 2014, at 8:15 AM, Ryan Schmidt <ryandesign at macports.org> wrote:
> On Jun 10, 2014, at 8:16 AM, Mark Brethen wrote:
>
>> Response from z88 developers below. I followed up with the suggested fixes already mentioned in this group.
>>
>> Begin forwarded message:
>>
>>> From: Z88Aurora Support <z88aurora at uni-bayreuth.de>
>>> Subject: AW: conflict with macports
>>> Date: June 10, 2014 at 2:32:41 AM CDT
>>> To: <deleted>
>>>
>>> Hello Mr. Brethen,
>>>
>>> unfortunately, it is not possible to simply change the location of the GTK+ files.
>
> Yes, it is possible for the people who packaged this Z88Aurora distribution to repackage it with files in a different location, and as we've discussed previously, that's what they must do to fix this conflict with MacPorts.
>
>>> To run Z88Aurora, you need the GTK+ package to be installed to /opt.
>>> I don’t know much about MacPorts, but how does the GTK+ package interfere with this? GTK+ will create the following folders/files:
>>>
>>> /opt/local
>
> [snip]
>
>>> Please ensure that this will not interfere with the existing MacPorts files in /opt and you will be fine.
>
> Installing files to /opt/local does interfere with MacPorts; they must not install files there.
>
> They are welcome to invent another prefix of their own choosing into which to put their files. Directories under /opt are a common choice. /opt/z88 or /opt/aurora for example would be fine choices. /opt/local is a poor choice because that has already been chosen by MacPorts.
>
>
>
I also just received a response from the Z88 support. He explained that they do see the necessity to work on the problem, but that I will have to wait until the next release because he claims that they will have to make changes in their source code.
I emphasized the significance of the dangers in their installation instructions, and suggested that they at least add a warning about installing with MacPorts until they get it fixed.
So, it sounds like they are now aware of the problem and will try to fix it. I have no idea about a timeline.
—Adam
More information about the macports-users
mailing list