DragonFly kernel List (threaded) for 2003-09
Re: /usr/dports now exists
We have "Darwinports" at www.opendarwin.org which also is called
on many systems.
We are making it as portable as is allowed :). People are trying to
use it on Solaris
, pure-darwin, OS X, and linux [and I believe on FreeBSD] all with
some level of
It would certainly be nice to work with DragonflyBSD as well but I
think dports and
dports would confuse the end user.
On Sep 8, 2003, at 7:03 PM, Matthew Dillon wrote:
Ok developers, I have created a /usr/ports override hierarchy for
DragonFly. This will allow DragonFly developers to modify FreeBSD
without us having to dup the FreeBSD ports hierarchy.
I have made the following changes:
* Created a 'dports' import, which should be checked out into
aka: cd /usr; cvs -d cvs checkout dports;
* Added /usr/src/usr.bin/relpath. You should cd into there ane
make obj; make; make install; make clean.
* Updated /usr/src/share/mk, so you should make install from
/usr/src/share/mk to install the new .mk files.
I have dup'd sysutils/cpdup as an example of a DragonFly port.
difference in the Makefile from a FreeBSD port is that it should
<bsd.dport.mk> instead of <bsd.port.mk>.
To create a DragonFly specific port override duplicate the FreeBSD
from /usr/ports into a new DragonFly port in /usr/dports (e.g.
and modify the Makefile to .include <bsd.dport.mk> instead of
<bsd.port.mk>, then make whatever additional modifications are
for the DragonFly version.
It should then be possible to build this new port either from the
DragonFly directory or from the original FreeBSD directory (it will
detect the override, generating a warning, and then cd into the
port to do the build).
Developers with commit privs: Please feel free to commit
cleanups in the new dports tree. Remember that this is
a temporary stopgap until we finalize how the new package
is going to work.