Opened 18 years ago
Closed 18 years ago
#10812 closed enhancement (fixed)
UPDATE: stunnel-4.1.6 update requested
Reported by: | d@… | Owned by: | yeled@… |
---|---|---|---|
Priority: | Low | Milestone: | |
Component: | ports | Version: | |
Keywords: | Cc: | ||
Port: |
Description
Hi,
There's a new version of stunnel available ( 4.16 ). I'd like to request the portfile is updated. Alternately, if someone can point me to doco on creating/updating port files, I'm happy to give it a shot.
Cheers, Dan
Change History (2)
comment:1 Changed 18 years ago by markd@…
Summary: | New Version of stunnel available → UPDATE: stunnel-4.1.6 update requested |
---|---|
Type: | defect → enhancement |
comment:2 Changed 18 years ago by markd@…
Resolution: | → fixed |
---|---|
Status: | new → closed |
This has been updated.
Note: See
TracTickets for help on using
tickets.
Docs for this are lacking right now. The following would work *if* the app had no changes that would require port script adjustments other than for the fetching of a new version. For minor point updates odds are there aren't. If the port install barfs then that is a good indication the guess was wrong. :)
Download the new tarball Get checksums of the new tarball (any and all that the current portfile uses):
Make a copy of the local portfile: cd sourcedir/stunnel ; cp Portfile Portfile.org ; edit Portfile and mod the version and checksums. Install the new port version (port install -vd stnnel). If it works ok then keep going. Make a unified diff of Portfile: diff -u Portfile.org Portfile >Portfile.diff Attach the Portfile.diff to a trac ticket and assign it to the port maintainer for review and update. State how it was tested (PPC 10.4.x, etc)