On Tue, May 14, 2002 at 11:32:19PM +1000, Bruce Evans wrote: > On Tue, 14 May 2002, Ruslan Ermilov wrote: > > > On Tue, May 14, 2002 at 06:21:41PM +1000, Bruce Evans wrote: > > > On Tue, 14 May 2002, Ruslan Ermilov wrote: > > > > > > > Yes. "make includes" has been modified to mean "build includes", > > > > and the new "make incsinstall" has been added to "install" them. > > > > So the correct sequence is "make includes incsinstall". > > > > > > > > I'm still unsure about the name; I'd have liked to rename it to > > > > "includesinstall" but that is too long. > > > > > > I still prefer something like > > > "__private_part_of_installworld_to_install_headers_dont_use_directly". > > > > > EPARSE; what does that mean? :-) > > > > "incsinstall" is the standard target which performs a part of a normal > > "install" -- installs C includes. > > Installing includes just corrupts the host environment unless the new > includes are consistent with the old libraries. If you know the build > system, the includes and the libraries well enough to know when it is > safe to use, then you know enough to never need it. > People might want to use it like that:
make world mv /usr/include /usr/include.old make incsinstall To remove stale includes. Previous version had "includes" that both built and installed includes, I have just split it in two parts. (I will add the par-includes to Makefile.inc1 tomorrow, FWIW.) Cheers, -- Ruslan Ermilov Sysadmin and DBA, [EMAIL PROTECTED] Sunbay Software AG, [EMAIL PROTECTED] FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age
msg38336/pgp00000.pgp
Description: PGP signature
