[MacPorts] #34931: Add "new" to port command

[MacPorts]

#34931: Add "new" to port command
-------------------------------------+--------------------------------------
 Reporter:  david.w.watson@…         |       Owner:  macports-tickets@…                   
     Type:  enhancement              |      Status:  new                                  
 Priority:  Normal                   |   Milestone:                                       
Component:  base                     |     Version:  2.1.1                                
 Keywords:                           |        Port:                                       
-------------------------------------+--------------------------------------

Comment(by ryandesign@…):

 No, I'm afraid there isn't any such feature at this time.

 You can view the [log:trunk/dports repository log] but of course it'll
 show you every change, not just those that result in a new port being
 added.

 As I was trying to ask above, it's not clear how a command like "port new"
 would work. How many new ports would it show you? Ten? The past week's
 worth? A month? Since you last ran the command? Since the beginning of
 time?

 Even if we had answers to the above, I'm not sure how we'd implement it. I
 don't think that the PortIndex stores the date when a port was first added
 to the index. And of course the PortIndex can be completely deleted and
 recreated; how would such a re-created index know when each port came into
 existence? And if it's not in the PortIndex, then MacPorts doesn't know
 it.

 This might be a candidate for a [browser:contrib contrib] script. If
 somehow given a range of dates, it could pull the Subversion log as above,
 and filter it to get only newly added Portfiles. The [browser:contrib
 /port-whatsnew port-whatsnew] script (which shows you the log of what's
 changed in a particular port since you installed it) might be a starting
 point. This would help you find newly added ports, but not new subports
 added to existing ports; to find new subports, a much more sophisticated
 algorithm would have to be used, which would probably have to download and
 look into the source code of each modified Portfile, which would probably
 make it prohibitively expensive in terms of bandwidth and CPU time.

-- 
Ticket URL: <https://trac.macports.org/ticket/34931#comment:3>
MacPorts <http://www.macports.org/>
Ports system for Mac OS