From owner-freebsd-afs@FreeBSD.ORG Tue Dec 16 17:10:39 2008 Return-Path: Delivered-To: freebsd-afs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4E3091065673 for ; Tue, 16 Dec 2008 17:10:39 +0000 (UTC) (envelope-from minimarmot@gmail.com) Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.173]) by mx1.freebsd.org (Postfix) with ESMTP id 1B19F8FC19 for ; Tue, 16 Dec 2008 17:10:39 +0000 (UTC) (envelope-from minimarmot@gmail.com) Received: by wf-out-1314.google.com with SMTP id 24so3457687wfg.7 for ; Tue, 16 Dec 2008 09:10:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=oSmGlK80nE8e8WoiGm9OeGsWPUqPUM+R+QP7MIK8FHM=; b=QMBfe7V3+FsapuDA8xb6ZNP0dFKsplbK0x+5bLShuu798zuyfGg/c943ENR6ok9DiK 6AJJFsHePxIJixYgIL45GUg0ao1DAjJy/4rZOoGf5CuQvbXmo7QErlCcruKQKWJpGzAv BItDMbK4DgSctCUTVWHwyIyO7vUqy/tl9sr+k= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=VSZLj8boSHD/flPfR7uDhzrC+9g43gaOruOaktP99Gw4zhgpNCXIQGVklcaDSPlp4A slUazufVtp7xRtZST4ppw6uu7615fS5ksM+l+BcCujfwGLw3YFs9NzRp5CE6GKwf3b9T dMYqZTMfNxSuviUxtXvPBqWQTZ1UzO4qlEbxg= Received: by 10.143.37.20 with SMTP id p20mr3387734wfj.51.1229447438777; Tue, 16 Dec 2008 09:10:38 -0800 (PST) Received: by 10.143.98.8 with HTTP; Tue, 16 Dec 2008 09:10:38 -0800 (PST) Message-ID: <47d0403c0812160910j92b5514y79652ee889e47423@mail.gmail.com> Date: Tue, 16 Dec 2008 12:10:38 -0500 From: "Ben Kaduk" To: "Palle Girgensohn" In-Reply-To: <1B1831E49644E24747EAC2A9@girgMac.local> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <37396849@bs1.sp34.ru> <01705453@bs1.sp34.ru> <49453004.9010107@linuxbox.com> <83768316_-_@bs1.sp34.ru> <4947B153.5060101@arcadebsd.org> <4947B7C4.8030004@arcadebsd.org> <1B1831E49644E24747EAC2A9@girgMac.local> Cc: freebsd-afs@freebsd.org Subject: Re: openafs server executables X-BeenThere: freebsd-afs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: The Andrew File System and FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Dec 2008 17:10:39 -0000 On Tue, Dec 16, 2008 at 9:46 AM, Palle Girgensohn wrote: > > > --On tisdag, ti 16 dec 2008 09.28.21 -0500 Derrick Brashear > wrote: > >> On Tue, Dec 16, 2008 at 9:14 AM, ElBarto wrote: >> >>> Derrick Brashear wrote: >>> >>>> >>>> >>>> So if I install openafs-client and openafs-server I'll have fs at >>>> two different place ? Seems ugly to me. >>>> >>>> >>>> Sounds subjective to me :) >>>> >>>> >>> >>> What do you propose for the path of the redundant binaries ? >>> >> >> Putting the extra copies in sbin > > This is stupid. Why two copies? What if server and client installations get > out of sync? That couldmake problems very hard to debug, since it is hardly > really well specified which of bin and sbin that comes first in the path. > The user will get confused, at best. > > It is really a very good argument for just having one port. I see no real > reason why there should be a separation. Some client binaries are only > needed when the server is installed, hence they need both. There seems to be > no clean cut between server and client in the upstream sources (client-only > and server-only installations share some binaries, e.g.), then we should not > force such a (non-clean) cut into the FreeBSD ports system either. There are some things that are clearly client, and some that are clearly server, and some that are shared. Now, we could probably argue for a while about exactly which ones are which, but that doesn't need to affect a conceptual breakdown into one or more FreeBSD ports. The three-way division mentioned elsewhere is, in fact, admirably suited to this situation: openafs-base for the shared commands openafs-server (DEPENDS openafs-base) for the server openafs-client (also DEPENDS openafs-base) is the client And one could also make a meta-package openafs that depends on both client and server, if one wants. The concern about having two different versions of fs, etc. is gone; one can even use the version-dependency tracking of FreeBSD ports to insure that the client and server utilities do not get out of sync. -Ben Kaduk