Date: Tue, 16 Dec 2008 12:10:38 -0500 From: "Ben Kaduk" <minimarmot@gmail.com> To: "Palle Girgensohn" <girgen@pingpong.net> Cc: freebsd-afs@freebsd.org Subject: Re: openafs server executables Message-ID: <47d0403c0812160910j92b5514y79652ee889e47423@mail.gmail.com> In-Reply-To: <1B1831E49644E24747EAC2A9@girgMac.local> References: <37396849@bs1.sp34.ru> <01705453@bs1.sp34.ru> <49453004.9010107@linuxbox.com> <83768316_-_@bs1.sp34.ru> <db6e3f110812160537ia5d1d4fm3d8587cd0dd731ce@mail.gmail.com> <4947B153.5060101@arcadebsd.org> <db6e3f110812160554p2f2748eatc8dc0f722c142350@mail.gmail.com> <4947B7C4.8030004@arcadebsd.org> <db6e3f110812160628y251d4246q281a1997e4e7ed6c@mail.gmail.com> <1B1831E49644E24747EAC2A9@girgMac.local>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Dec 16, 2008 at 9:46 AM, Palle Girgensohn <girgen@pingpong.net> wrote: > > > --On tisdag, ti 16 dec 2008 09.28.21 -0500 Derrick Brashear > <shadow@gmail.com> wrote: > >> On Tue, Dec 16, 2008 at 9:14 AM, ElBarto <elbarto@arcadebsd.org> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?47d0403c0812160910j92b5514y79652ee889e47423>