ports/78774: Update net/libdnet 1.9 -> 1.10

[Jonathan]

>Number:         78774
>Category:       ports
>Synopsis:       Update net/libdnet 1.9 -> 1.10
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-ports-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sun Mar 13 12:00:15 GMT 2005
>Closed-Date:
>Last-Modified:
>Originator:     Jonathan
>Release:        5.0
>Organization:
N/A
>Environment:
FreeBSD it.starts.with.W 5.0-RELEASE FreeBSD 5.0-RELEASE #0: Thu Aug 28 21:09:30 IDT 2003     root@:/usr/obj/usr/src/sys/SERVER  i386
>Description:
Update libdnet to 1.10. Add python support.
That was less easy than it might have been.
Logic of if's:
python is installed (1), WITH_PYTHON selected: no banner, add support.
python is installed, WITH_PYTHON not selected: no banner, add support.
python not installed, WITH_PYTHON selected: no banner, install python(2), add support.
python not installed, WITH_PYTHON not selected: show banner, no support.

Note the hack of inclusion of bsd.python.mk. This is done to generalize
PYTHON_VERSION. If you can suggest a better alternative, I'm willing to
learn.

This file would be more readable if there was a version of PYTHON_SITELIBDIR
without LOCALBASE, for inclusion into PLIST_FILES. But there isn't.

I realize now I could have made my life much easier if I only cared
about WITH_PYTHON and not about if it's actually installed. Oh well...
Is there any point in using OPTIONS if there's only one option?

1 - ${LOCALBASE}/bin/python exists.
2 - should be done because of BUILD_DEPENDS. untested.


>How-To-Repeat:
N/A
>Fix:
http://www.sl0th.org/FreeBSD/libdnet-1.9-1.10.diff
>Release-Note:
>Audit-Trail:
>Unformatted: