#27588: users are not aware that xz-devel is outdated and they should replace it by xz ----------------------------------+----------------------------------------- Reporter: vinc17@… | Owner: afb@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: xz xz-devel | ----------------------------------+----------------------------------------- Comment(by ryandesign@…): Replying to [comment:4 afb@…]:
Fixed, r74169.
Also, the version needs to be increased, and users need to be prevented from attempting to install the port, and all the lines relating to installing the port can be removed. r74172. Replying to [comment:5 afb@…]:
Pretty much all the development ports conflict with their stable counterparts,
Yes they do.
so adding explicit conflicts is somewhat redundant
Adding explicit conflicts is absolutely necessary; it prevents a user from wasting time building a port if it won't be able to activate anyway due to conflicting files.
especially if they already have implicit file conflicts.
Which implicit file conflicts are you talking about?
But it's a pretty strange way to version things, either way.
What is? -- Ticket URL: <https://trac.macports.org/ticket/27588#comment:6> MacPorts <http://www.macports.org/> Ports system for Mac OS