Date: Wed, 09 Apr 2003 07:26:46 +0200 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: Garance A Drosihn <drosih@rpi.edu> Cc: cvs-src@FreeBSD.org Subject: Re: installing *.h files in /usr/include Message-ID: <29024.1049866006@critter.freebsd.dk> In-Reply-To: Your message of "Wed, 09 Apr 2003 01:14:31 EDT." <p05200f18bab95c1d7eff@[128.113.24.47]>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <p05200f18bab95c1d7eff@[128.113.24.47]>, Garance A Drosihn writes: >At 6:53 AM +0200 4/9/03, Poul-Henning Kamp wrote: >>In message <076d01c2fe0c$6c865200$52557f42@errno.com>, "Sam Leffler" writes: >> >> > Who said anything about installing stuff in /usr/include? >>> >> > .h files hold definitions needed by 1 or more pieces of code. >> > You're just obfuscating your code. >> >>You are in fact talking about installing things in /usr/include, >>have you forgotten that I raised this subject a short time ago ? >> >>The only way I can say "foo.h" should not be installed under >>/usr/include is by not calling it something which matches "*.h" > >I thought this had been fixed, so you could specify a list of *.h >files to *not* install in /usr/include? There actually seems to be some per-directory stuff now, so I guess I can name the file adlink.h now. It doesn't help me any with geom/*.h where only some of the files should be installed though :-( -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?29024.1049866006>