[108866] trunk/dports/net/samba3/Portfile

[Ryan Schmidt]

On Aug 4, 2013, at 12:02, Jeremy Huddleston Sequoia wrote:

> dylib ids are all messed up in samba3 after this update.  Reverting and rebuilding gets a sane samba3 install:
> 
> 
> Warning: ID load command in /opt/local/lib/samba3/libtevent.dylib.0.9.11, arch x86_64 (belonging to port samba3) contains relative path

This is new to me and I'm not sure what to do about it.


> Could not open bin/libtalloc.dylib.2: Error opening or reading file (referenced from /opt/local/lib/samba3/libtevent.dylib.0.
> 9.11)

I did notice this after committing. I spent a couple hours investigating. I saw the pages of install_name_tool commands the portfile already contains. Then I tried to figure out why the samba build system is so awful and how to fix it properly. I looked at Homebrew's formula, which doesn't seem to do anything special, but they are on an earlier version of samba 3 which might build differently. Then I found that the samba developers (or at least people responding in their issue tracker) don't seem to care about OS X at all; say that OS X does not work; and suggest that people use Linux instead. Apple of course no longer includes Samba in OS X as of Lion presumably because of GPL 3. Then I saw that samba 4 has switched to a new build system, and that a bug report about the same install_name problem has already been filed against version 4 in February, with no response or fix. And then there are all the open MacPorts tickets about samba ports that have gone unresolved. I then briefly considered "svn rm"ing the samba ports and being done with it, before just closing the window and trying to work on happier things.

But perhaps I can just add a line or two to the existing install_name_tool madness to fix this one problem.

A ticket has already been filed:

https://trac.macports.org/ticket/39992