Need Complete Idiots Guide To Fixing My Ports

Roland Smith rsmith at
Mon Jul 7 18:16:56 UTC 2014

On Mon, Jul 07, 2014 at 09:29:12AM -0500, Tim Daneliuk wrote:
> So the portmaster is nagging me to update my ports to the newfangled ports
> system.  I  glanced at the docs and it looks like way more effort than I
> want to put into it.  I have REALLY simple ports of things like python
> programs and their docs.
> Is there some simple, 4 step process I can apply to my ports without having
> to resort to testing with poudriere and the like?  (Because I won't bother,
> I'll just quit supporting the FreeBSD ports model and release stuff
> on my own website ...)

1) Read, /usr/ports/Mk/,
   porters handbook
2) Start with a new empty Makefile, to get rid of all the cruft.
3) Re-write the Makefile with the above references and other Python ports that
were already fixed. If you're not changing a version, you can keep the distinfo.
If you are using distutils, you might not even have to write a pkg-plist.
4) Run `env DEVELOPER=yes make stage && make check-plist && make package` *as
a normal user* and portlint on your new port to test.

I've got some patches for Python-based ports in the queue it you want to have a look at

Possibly 190674 is a-typical because this software has a Makefile instead of a This is because I'm combining the script and its dedicated modules into
a single zip-file for convenience.

[plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated]
pgp: 5753 3324 1661 B0FE 8D93  FCED 40F6 D5DC A38A 33E0 (keyID: A38A33E0)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <>

More information about the freebsd-questions mailing list