Date: Sat, 18 Mar 1995 10:36:53 -0800 (PST) From: "Rodney W. Grimes" <rgrimes@gndrsh.aac.dev.com> To: bde@zeta.org.au (Bruce Evans) Cc: bde@zeta.org.au, CVS-commiters@freefall.cdrom.com, cvs-sys@freefall.cdrom.com, davidg@Root.COM, phk@ref.tfs.com Subject: Re: cvs commit: src/sys/libkern locc.c random.c scanc.c skpc.c libkern Message-ID: <199503181836.KAA21691@gndrsh.aac.dev.com> In-Reply-To: <199503180911.TAA14031@godzilla.zeta.org.au> from "Bruce Evans" at Mar 18, 95 07:11:54 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> > >And my grepping of the source tree turned up no one that directly > >inclues sys/systm.h, but it *is* included by vm_page.h. I have > >yet to search the source tree for that one. > > It's only included if KERNEL and DIAGNOSTIC are defined. I was aware of that. I was going more after should we even be installing /usr/include/vm/vm_page.h at all. > >This does bring up the question of should we be installing all the > >files we are in /usr/include/sys. As I am about to rewrite the > >/usr/include Makefile to clean up all the mkdir/chown/chmod this > >would be a *very* good time to clean up *exactly* what header > >files we install into /usr/include/sys. > > Traditional system internals should be there. I don't think it can > be cleaned up quickly. There are too many interdependencies. I may not be able to implement the *policy* of which files get installed, but I can implement the *method* that allows us to select which ones we install. The current Makefiles can't, as they blindly use tar to copy the whole directories. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199503181836.KAA21691>