Changes between Initial Version and Version 2 of Ticket #54605


Ignore:
Timestamp:
Aug 15, 2017, 10:13:39 AM (7 years ago)
Author:
ryandesign (Ryan Carsten Schmidt)
Comment:

The command port file foo will tell you where the Portfile for port foo is located.

The registry contains a copy of the Portfile as it appeared when you installed the port. This may not be the current version of the Portfile, and if you're going to submit a patch, it should be based on the current version, which is in the sources directory, or, as Ken said, in our GitHub repository.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #54605 – Description

    initial v2  
    22https://guide.macports.org/#development.patches.portfile
    33
    4 It tells you how to make a copy and generate patch for a Portfile, but it does not tell you where to find the original Portfile.  Looking on my system with find /opt/local grep|portname|grep Portfile, I find two candidates, one somewhere in /opt/local//var/macports/sources/rsync.macports.org/release/tarballs/ports and another somewhere in /opt/local//var/macports/registry/portfiles/ and they appear slightly different. 
     4It tells you how to make a copy and generate patch for a Portfile, but it does not tell you where to find the original Portfile.  Looking on my system with find /opt/local grep|portname|grep Portfile, I find two candidates, one somewhere in /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports and another somewhere in /opt/local/var/macports/registry/portfiles/ and they appear slightly different. 
    55
    66Even if this is an idiosyncrasy in my system, the guide section should include the default location of the Portfile to be used to generate patches.