#29276: update cmus to 2.4.0 ---------------------------------------+------------------------------------ Reporter: devnull.macports@… | Owner: milosh@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: haspatch | Port: cmus ---------------------------------------+------------------------------------ Changes (by jmr@…): * keywords: cmus => haspatch * owner: macports-tickets@… => milosh@… * version: 1.9.2 => * cc: devnull.macports@… (removed) Comment: Please remember to cc the maintainer. You do not need to be in cc when you are the reporter. Are any of the dependencies not being found? Telling the configure script not to use them in that case isn't what we want; the problem needs to be fixed. Ports should use exactly what they declare dependencies on. Also, note that the initial revision for a new version should be 0. -- Ticket URL: <https://trac.macports.org/ticket/29276#comment:3> MacPorts <http://www.macports.org/> Ports system for Mac OS

#29276: cmus: update to 2.4.0 ----------------------------------------+----------------------------------- Reporter: devnull.macports@… | Owner: milosh@… Type: update | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: haspatch Port: cmus | ----------------------------------------+----------------------------------- Changes (by ryandesign@…): * status: new => closed * cc: ryandesign@… (added) * resolution: => fixed Comment: Replying to [comment:4 devnull.macports@…]:

If the wanted behavior is to fail when the dependencies can't be found, 'y' is the right choice. It's just that most likely all other packages that use autoconf don't behave this way.

I don't understand what you're saying. The desired behavior is for a port to declare dependencies on the other ports it uses, and for it to use the other ports it declares dependencies on. For example, cmus does not use flac and does not declare a dependency on flac, unless the flac variant is selected, in which case flac is used and a dependency is declared. This is how we want ports to work. I understand that it is common for software developers to be "helpful" and build their configure scripts so that they automatically use certain optional features if they're available and don't complain about them if they're not, but this "helpfulness" is inappropriate in MacPorts, where we want to be explicit about what other libraries are being used. I updated the port to 2.4.0 in r78434. -- Ticket URL: <https://trac.macports.org/ticket/29276#comment:5> MacPorts <http://www.macports.org/> Ports system for Mac OS