#48461: Installing caffe installs libgcc-devel despite not depending on it. --------------------------+------------------- Reporter: jrd-freak@… | Owner: hum@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: | Keywords: Port: caffe | --------------------------+------------------- Comment (by jrd-freak@…): I suppose so, as this is ultimately user error. I wonder though how exactly I could have found out about it. Does installing `libgcc-devel` inform me at some point that it will deactivate `libgcc`? I do not remember, but I did not have to do anything to resolve the conflict, as far as I remember. Also, is it generally the case that such beta-ports are used as drop-in replacements in conflict situations or is it just `libgcc`? Where can I find documentation on the topic? -- Ticket URL: <https://trac.macports.org/ticket/48461#comment:5> MacPorts <https://www.macports.org/> Ports system for OS X