openafs port(s) in general (was: Re: openafs server executables)

[Boris Samorodov]

ElBarto <elbarto at arcadebsd.org> writes:

> I kind of disagree for splitting the openafs ports cause as you say
> some commands are useful (more or less) for both client and server
> part, but as it seems that it's going to be that way, I want the port
> to be clean and with no redundancy.

Let me elaborate on this a little. First off, how the port will look
like is a matter of discussion. I'm open to suggestions. As well as
someone may take the port I've done and suggest his version. ;-)

My intention is following. The main port (say, net/openafs) will be one
and will install the whole thing. And there will be some options (say
WITH_SERVER_ONLY, WITH_CLIENT_ONLY) which will allow installing the
relevant part. (BTW in this case who do care if a slave ports
like net/openafs-server and/or openafs-client exist?)

While discussing port(s) questions I was told that server and client
parts are totally different and don't have anything in common. And if
they do have then my ports are wrong. That and only that pushed me to
find out which file belongs to which part.

If you (read: developers, users and admins of OpenAFS on FreeBSD) give
me a definite answer then I'll create such a port. You may even give
a triple division: those files are server, those file are client,
while those are common! I'll deal with it. Thanks.


WBR
-- 
Boris Samorodov (bsam)
Research Engineer, http://www.ipt.ru Telephone & Internet SP
FreeBSD committer, http://www.FreeBSD.org The Power To Serve