Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 29 Sep 1995 14:24:09 -0700 (PDT)
From:      "Rodney W. Grimes" <rgrimes@GndRsh.aac.dev.com>
To:        mark@grondar.za (Mark Murray)
Cc:        wollman@lcs.mit.edu, mark@grondar.za, gibbs@freefall.freebsd.org, ache@freefall.freebsd.org, CVS-commiters@freefall.freebsd.org, cvs-sbin@freefall.freebsd.org
Subject:   Re: cvs commit: src/sbin Makefile
Message-ID:  <199509292124.OAA00787@GndRsh.aac.dev.com>
In-Reply-To: <199509292034.WAA22635@grumble.grondar.za> from "Mark Murray" at Sep 29, 95 10:34:07 pm

next in thread | previous in thread | raw e-mail | index | archive | help
> 
> > <<On Fri, 29 Sep 1995 22:11:47 +0200, Mark Murray <mark@grondar.za> said:
> > 
> > > Right now we have two wrongs making a right. We _have_ to have a make
> > > with no MAKE_EBONES to make the clean distribution, followed by a nasty
> > > hack to make the tainted distribution. Why can we not have "make
> > > distribution" do it properly the first time? Sure we will need to fix
> > > the make files, but that can of worms has been brewing for a while...
> > 
> > Not everyone's build environment is based on `make release' and `make
> > distribute'.
> 
> Granted. Then the logic should be "if the eBones directory exists, build
> eBones _unless_ asked not to", rather than "the directory must be present
> _and_ permission must be granted to build eBones".
> 
> This would mean that secure and eBones can be added to the system just
> by dropping them in.

At this point in this conversation I would suggest to go read the FreeBSD
mail archives for similial discussions and the rational that was used when
makeing the decision for that state of the defaults.

It has something to do with the path of least surprize to protect people
from ``unknowingling'' building a set of binaries that could not be
exported.  You will find almost _all_ software that has these types of
restrictions in it requires 2 things to be done, the addition of the
non exportable code source files and the turning of a knob to enable it.

I would also suggest that the ad hoc, without white paper, and review
changing of the FreeBSD source tree in this area just stinks.  Insignificant
discussion before action has again occured :-(.

-- 
Rod Grimes                                      rgrimes@gndrsh.aac.dev.com
Accurate Automation Company                 Reliable computers for FreeBSD



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199509292124.OAA00787>