From my POV, I just want it to work, and one way is as good as another. :-) But I think Ryan's point is that the originators should ideally deal with this sort of thing, and perhaps it should get patched or otherwise worked around in MacPorts only if they refuse to. That's probably a better solution insofar as it would also help people using homebrew or fink, or building directly; not to mention that workarounds have a growing maintenance burden of their own. But the time required seems to be proportional to the square of the number of people involved, so those of us who just want to do "port upgrade outdated" on a regular basis, and have nothing fail, would have longer to wait. :-)
> On Apr 30, 2017, at 07:05, Ken Cunningham <[email protected] > <mailto:[email protected]>> wrote: > > I started working on such a library last summer (see this thread: > )https://lists.macports.org/pipermail/macports-dev/2016-August/033453.html > <https://lists.macports.org/pipermail/macports-dev/2016-August/033453.html> > I updated it yesterday and indeed it builds gss on 10.6 nicely. > > See: https://github.com/kencu/snowleopardfixes > <https://github.com/kencu/snowleopardfixes> > > I also have a port file to install the library, and a small block to add to > the port files of ports that need it. > > This was one of the reasons I was looking for a 'default' portgroup that > could be used to add a bit of code to all port files on a given system. > > Ken
signature.asc
Description: Message signed with OpenPGP
