Re: [pkg-GNUstep-maintainers] Re: Conflicts between FHS and GnuStep
On Mon, Aug 23, 2004 at 02:53:52PM -0700, Brent Fulgham wrote:
>
> --- Manoj Srivastava <srivasta@debian.org> wrote:
>
> > Umm, no. That would be stretching it. All kinds of
> > application frameworks already place files in
> > /usr/include, there is no reason why GNUStep should
> > be granted a special dispensation.
>
> It looks to me like languages like Python and Lisp
> always put their equivalent "developer use" files in
> /usr/lib. /usr/include/ is where they put their
> C-interoperability stuff.
To be pedantic, they usually use /usr/share/ for such file
to mark them architecture independent. Neither /usr/lib or /usr/include
are.
> Now, I can't make an argument (with a straight face
> at least) that Objective-C is so different from C(++)
> that it needs to store its data in a separate place,
> so the argument is a bit moot.
It is not Objective-C vs C++, but GNUStep Objective-C
vs. others Objective-C frameworks that use /usr/include.
Also GNUstep headers are not in the default search path of
gcc.
Cheers,
--
Bill. <ballombe@debian.org>
Imagine a large red swirl here.
Reply to: