If it is, I would suggest a split like:
freebsd-nfs-server
freebsd-nfs-client
freebsd-nfs-common
since a server probably doesn't want to waste memory on
nfsiod either.
Comments?
I like the idea of spliting. I am unsure whether we should aim for server
instalation without client binaries. The wasting of disk on server would
be small, programs like showmount are needed on both sides anyway.
For the packaging and missing functions, would be possible to i.e. create
small static lib inside with them or use the same source files from
all build dirs, like:
SRCS= nfsd.c ../../extra/nfssvc.c
SRCS= mountd.c getmntopts.c ../../extra/getvfsbyname.c ../../extra/nfssvc.c
SRCS= nfsiod.c ../../extra/getvfsbyname.c
Petr
--
To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/alpine.lrh.2.02.1106290722420.3...@sci.felk.cvut.cz
