Contents 1. [**1** Case example](upgrading-a-port.html#TOC-Case-example) 1. [**1.1** Downloading latest upstream source](upgrading-a-port.html#TOC-Downloading-latest-upstream-source) 2. [**1.2** Calculating md5](upgrading-a-port.html#TOC-Calculating-md5) 3. [**1.3** Editing the portfile](upgrading-a-port.html#TOC-Editing-the-portfile) 4. [**1.4** Creating the patch](upgrading-a-port.html#TOC-Creating-the-patch) 5. [**1.5** Testing the patched portfile](upgrading-a-port.html#TOC-Testing-the-patched-portfile) 6. [**1.6** Activating the new version](upgrading-a-port.html#TOC-Activating-the-new-version) 7. [**1.7** Submitting the patch to MacPorts](upgrading-a-port.html#TOC-Submitting-the-patch-to-MacPorts)

In this example, we update the portfile for gnustep-base. This is just an example.

To find out the URL where the upstream source is located, do:

port cat gnustep-base 

Check whether a newer version is available at that download location and download it, in this case gnustep-base-1.16.3.tar.gz

Calculate the md5 checksum of the upstream source with

md5 gnustep-base-1.16.3.tar.gz  MD5 (gnustep-base-1.16.3.tar.gz) = 32ae302922a0a6e14c7008a105014bba

Copy the portfile first so that we can create a patch later:

cp $(port file gnustep-base) $(port file gnustep-base).orig port edit gnustep-base

Change version to 1.16.3 Change md5 to the value calculated before

diff -u $(port file gnustep-base).orig $(port file gnustep-base) > gnustep-base.patch

Now build it with

port rpm gnustep-base

In order to activate the new version so that it is used when builting additional software, you need to do in addition:

port archive gnustep-base port upgrade -n gnustep-base

Finally, check that your activated version is really the new one with

port installed gnustep-base

Search whether a ticket already exists, if not submit a new one with the patch attached.