Building ports for DragonFlyBSD

[Oliver Eikemeier]

Joerg Sonnenberger wrote:

On Tue, Aug 10, 2004 at 01:36:01AM +0200, Oliver Eikemeier wrote:
Joerg Sonnenberger wrote:
A DragonFly (override) port should use bsd.dfport.mk. If you want to
support DragonFly in a normal FreeBSD port, no additional magic beside
e.g. CPP (__DragonFly__) should be needed.
Let's take security/portaudit as an example. Matthew imported the new
pkg_install version July 30th 2004, so I do not need to depend on the
port. I'm supposed to conditionalize that on __DragonFly_version, but
this information is not available in the ports Makefile.
I'm not sure what you mean. We don't update __DragonFly_version every
time we change something, because that would still happen to often.
In the port I have

. if ${OSVERSION} < 492000 || ${OSVERSION} >= 500000 && ${OSVERSION} < 
502120
RUN_DEPENDS=
	${LOCALBASE}/sbin/pkg_info:${PORTSDIR}/sysutils/pkg_install-devel
. endif

I could change this to

. if !defined(DFPORTSDIR) && ${OSVERSION} < 492000 || ${OSVERSION} >= 
500000 && ${OSVERSION} < 502120
RUN_DEPENDS=
	${LOCALBASE}/sbin/pkg_info:${PORTSDIR}/sysutils/pkg_install-devel
. endif

but this won't work on DragonFly-1.0.

For a port, IMO you can for the moment just depend on a current system,
e.g. I have to change bsd.port.mk now because x11/xorg-clients needs
some more magic. If you really insist on checking __DragonFly_version,
use sed / grep on /usr/include/sys/param.h.
Have you send the patches to Eric Anholt or x11 at xxxxxxxxxxx? The 
override thing seems to be maintenance intensive, but maybe I wrong 
here...

-Oliver