installing *.h files in /usr/include

Garance A Drosihn drosih at rpi.edu
Tue Apr 8 22:14:37 PDT 2003


At 6:53 AM +0200 4/9/03, Poul-Henning Kamp wrote:
>In message <076d01c2fe0c$6c865200$52557f42 at 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 at gilead.netel.rpi.edu
Senior Systems Programmer           or  gad at freebsd.org
Rensselaer Polytechnic Institute    or  drosih at rpi.edu


More information about the cvs-src mailing list