New Ticket     Tickets     Wiki     Browse Source     Timeline     Roadmap     Ticket Reports     Search

Ticket #26028 (new enhancement)

Opened 5 years ago

Last modified 5 months ago

Add feature to show changes between port versions

Reported by: sewebster@… Owned by: macports-tickets@…
Priority: Low Milestone:
Component: base Version:
Keywords: Cc: and.damore@…, snc@…, ryandesign@…, macosforge@…, macports@…, macports.org@…
Port:

Description

Several times when I have run the port outdated command and seen that there was an update available to one of my installed ports, I have wondered what it is that has changed between the two versions. I don't know of an easy way to get this information, other than browsing the revisions in the source on trac.

It may be possible to create a command line tool that displays this information. I guess it would have to take a portname and two versions as inputs, then look through the revision history to find when the versions changed, and then compile a list of all the change descriptions.

Of course if there were changelogs it could just output that.

Change History

comment:1 Changed 5 years ago by sewebster@…

I guess an easier way for this to work from the user perspective would be to have a command like port diff portname and just compare the installed version with the available version.

comment:2 Changed 5 years ago by blb@…

If you're thinking along the lines of having it display the commit message, note that many of those aren't going to say much beyond "update to version x.y.z" meaning it won't be any more informative than outdated's "1.2.3 < 1.2.4".

comment:3 Changed 5 years ago by sewebster@…

Right. I suppose what might be less obvious is changes between revisions, which would be macports-only. But perhaps these are of limited interest to many users.

comment:4 Changed 5 years ago by and.damore@…

  • Cc and.damore@… added

Cc Me!

comment:5 Changed 5 years ago by snc@…

  • Cc snc@… added

Cc Me!

comment:6 Changed 5 years ago by ryandesign@…

  • Cc ryandesign@… added

Try "port-whatsnew", available now in the contrib section of the repository. See r70612.

comment:7 Changed 5 years ago by sewebster@…

Wow, thats fantastic! Thanks.

Possible items for future versions could be:

  • support more than one port argument
  • support pseudoports
  • or, I guess a subset of the previous point, make it easy to spit out the changes to all outdated ports, e.g.
    port echo outdated | cut -f 1 -d" " | xargs -n 1 ./port-whatsnew.sh
    

comment:8 Changed 4 years ago by macosforge@…

  • Cc macosforge@… added

Cc Me!

comment:9 Changed 9 months ago by macports@…

  • Cc macports@… added

Cc Me!

comment:10 Changed 5 months ago by macports.org@…

---<dup>---

Last edited 5 months ago by macports.org@… (previous) (diff)

comment:11 Changed 5 months ago by macports.org@…

  • Cc macports.org@… added

Cc Me!

Note: See TracTickets for help on using tickets.