"J. Lewis Muir" <jlmuir%imca-cat.org@localhost> writes: > On 2/18/16 8:44 AM, Greg Troxel wrote: >> While I realize that this is arguably an upstream bug, it also seems >> that Darwin shlib issues are frequent (perhaps in most packages that >> don't use GNU libtool??). I wonder if pkgsrc should have some sort of >> fixup infrastructure, sort of like how script paths are patched. > > My feeling is that it's better to check for problems and report them > (like with PKG_DEVELOPER=yes) than to just fix them up behind the > scenes. By reporting them, hopefully upstream can be corrected. Certainly, but... > Of course, with infrastructure that automatically fixes things up, that > would make less work for the package maintainer. I am talking about easing the burden of adding workarounds. OS X is odd, and that means that these issue will continue to be common. Your changes were slightly hard to follow, and on reflection seem like they could be factored out into a list of libraries to patch and a list of dependencies to adjust, so that there would be two variables set, and no need for the open-coded version.
Attachment:
signature.asc
Description: PGP signature