Opened 5 years ago

Last modified 5 years ago

#54315 new submission


Reported by: RJVB (René Bertin) Owned by:
Priority: Normal Milestone:
Component: contrib Version:
Keywords: Cc: neverpanic (Clemens Lang), raimue (Rainer Müller), 1-61803


Anyone creating new ports or upgrading existing ones has probably had the experience of discovering when activating the port that certain of its files are already provided by another port s/he has installed.

This script aims to help with this, allowing to compile a list of all such files and the port(s) providing them after destroot'ing the port but before actually installing it. It can do the same thing with a destroot-equivalent of a project that hasn't yet been port'ified, and has a -v argument to inverse the logic and report new files.

I find the script especially useful for large ports containing hundreds (or even thousands) of files.


Attachments (1)

port-check-conflicts.tcl (8.5 KB) - added by RJVB (René Bertin) 5 years ago.

Download all attachments as: .zip

Change History (5)

Changed 5 years ago by RJVB (René Bertin)

Attachment: port-check-conflicts.tcl added

comment:1 Changed 5 years ago by raimue (Rainer Müller)

Cc: raimue added

Is this meant for inclusion to macports-contrib or what action is expected on this ticket?

comment:2 Changed 5 years ago by RJVB (René Bertin)

If you think it's useful enough for that, sure. My intention was just to share (and maybe get some constructive feedback if certain things could really have been done more elegantly or efficiently).

comment:3 Changed 5 years ago by raimue (Rainer Müller)

For getting comments a ticket feels like the wrong place, better use the mailing list for that. Tickets are meant to document that we need to take an action (fix a bug, implement a feature request). With this I do not see at which point I would consider it "resolved" as it does not describe an issue.

comment:4 Changed 5 years ago by 1-61803

Cc: 1-61803 added
Note: See TracTickets for help on using tickets.