Subject: Re: Compile of routed in -current ? ....
To: matthew green <firstname.lastname@example.org.Oz.Au>
From: Greg A. Woods <email@example.com>
Date: 07/05/1995 17:06:59
[ On Fri, June 30, 1995 at 10:35:54 (+1000), matthew green wrote: ]
> Subject: Re: Compile of routed in -current ? ....
> i *strongly* disagree with the idea of *building* things into
> /usr/src/include. i'm unsure about the idea as a whole at the
> moment, but if it was adopted, it would need to build to some
> other place.
Well unless you're lucky enough to have a machine on which to simply
play with full builds on, then this is the *only* way to do things
As an applications programmer I woudl freak out if someone were to
install /usr/include all the time.
"Building" stuff into /usr/src/include allows the O/S build to proceed
relatively invisibly to other work that might be happening on the same
system, and provides the three-stage process necessary to ensure the
quality control of stuff installed in /usr/include.
(This is, of course, assuming the current contents of /usr/src/include
were moved into those parts of the tree where they have associated
responsibilities, and yes, everything does have a logical place if you
just think about it for a moment.)
Greg A. Woods
+1 416 443-1734 VE3TCP robohack!woods
Planix, Inc. <firstname.lastname@example.org>; Secrets Of The Weird <email@example.com>