Date: Wed, 1 May 1996 11:56:18 +0100 (BST) From: Paul Richards <p.richards@elsevier.co.uk> To: FreeBSD-current@FreeBSD.org (FreeBSD current mailing list) Subject: Re: cvs commit: ports/net/socks5 Makefile Message-ID: <199605011056.LAA21427@cadair.elsevier.co.uk> In-Reply-To: <199604301626.JAA13472@GndRsh.aac.dev.com> from "Rodney W. Grimes" at Apr 30, 96 09:26:28 am
next in thread | previous in thread | raw e-mail | index | archive | help
I've redirected this to -current rather than committers.
In reply to Rodney W. Grimes who said
>
> > Give me a few days to look into the other ports.
>
> Be careful in your judgement call. Perhaps if you could produce a list
> of the files that end up in local/etc if all of the ports are installed
> and label them with your judgement then pass that to the list for some
> other judgements and rational.
>
This is a bit silly. It doesn't matter what ports install what where. What
we need to do is evaluate what the possible requirements are and agree
a directory structure that fits.
A few things have come up recently. I think a bit of a step back is needed
and a look at the whole NFS issue and it's impact on file layout is needed.
The ports issue and the /etc issue have both shown up some warts in the
current layout.
I'm beginning to think that all of /usr should be shareable across a single
architecture (not much point in a wider requirement since they're binaries
in the main) with /usr/share containing architecture independant stuff, as
it already should.
/usr/local would then contain all shareable aspects of ports.
I think perhaps we should have a /local directory for host specific files
that are not part of the generic OS but are added by local admins. It
would have a mirror of / i.e. /local/etc /local/var and so on.
This makes me happy since the ports are still segregated from the main OS. The
NFS folks are happy since they can export /usr and still have host specific
config files that the binaries will pick up from whatever machine they are
run on.
I'm not won around on the /usr/arch/i386 idea yet since if /usr is
architecture dependant then a /usr/arch/{i386,sparc,alpha} seems wrong
somehow. Maybe /usr/config would be better since what will go there is
architecture dependant config files such as /etc templates and syscons
maps. They should all be shareable so it won't break the NFS model above.
Any other possible uses I might not have thought of?
--
Paul Richards. Originative Solutions Ltd. (Netcraft Ltd. contractor)
Elsevier Science TIS online journal project.
Email: p.richards@elsevier.co.uk
Phone: 0370 462071 (Mobile), +44 (0)1865 843155
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199605011056.LAA21427>