#37601: textmate2@r9339: conflicts with libc-headers --------------------------+---------------------- Reporter: ciserlohn@… | Owner: cal@… Type: defect | Status: reopened Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Resolution: | Keywords: Port: textmate2 | --------------------------+---------------------- Changes (by ryandesign@…): * status: closed => reopened * cc: mfeiri@… (added) * resolution: fixed => Comment: The `conflicts` keyword is for activation-time conflicts, i.e. ports that install the same files. That's not the case here; here we have a build- time conflict, for which the `conflicts_build` keyword from the conflicts_build portgroup is used. However, it seems a pretty severe problem for any port to install a header like stdio.h that masks the version the OS provides, especially if its version is not compatible with the system's version. Michael, why does libc-headers need to do that? I would think that would cause a whole lot of ports to fail to build. Can libc-headers not install that file, or can it install it to a different location? -- Ticket URL: <https://trac.macports.org/ticket/37601#comment:4> MacPorts <http://www.macports.org/> Ports system for Mac OS