To port or not to port
Adam Weinberger
adamw at freebsd.org
Sat May 17 18:18:06 PDT 2003
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
>> (05.17.2003 @ 1709 PST): Colin Percival said, in 0.6K: <<
> Is there any general rule for when code should be an independent port
> vs. when it should be included in a different port?
> For the next version of security/freebsd-update I've written a binary
> diff/patch tool; it can certainly be used on its own, but I think it's most
> important user will be freebsd-update.
> Should I submit this as a separate port, or just build it as part of
> freebsd-update?
>> end of "To port or not to port" from Colin Percival <<
If they may get updated independently, or if people may want one without
the other, take a look at the structure of sysutils/cdrtools and
sysutils/mkisofs.
# Adam
- --
Adam Weinberger
vectors.cx >> adam at vectors.cx
FreeBSD.org << adamw at FreeBSD.ORG
#vim:set ts=8: 8-char tabs prevent tooth decay.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (FreeBSD)
iD8DBQE+xt+so8KM2ULHQ/0RAobMAJsGEcULu0EtweTWKFv4LBVm2mopmwCfbSMo
aBzNERUjSl+QoOTN6bBcP9I=
=OqZ2
-----END PGP SIGNATURE-----
More information about the freebsd-ports
mailing list