Date: Wed, 9 Apr 2003 01:14:31 -0400 From: Garance A Drosihn <drosih@rpi.edu> To: "Poul-Henning Kamp" <phk@phk.freebsd.dk>, "Sam Leffler" <sam@errno.com> Cc: src-committers@FreeBSD.org Subject: Re: installing *.h files in /usr/include Message-ID: <p05200f18bab95c1d7eff@[128.113.24.47]> In-Reply-To: <27158.1049864000@critter.freebsd.dk> References: <27158.1049864000@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
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? If not, how about calling the file something like blah.hc ? -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?p05200f18bab95c1d7eff>