Hello, On Fri, Nov 07, 2003 at 08:19:06PM +0100, Sven Luther wrote: > On Fri, Nov 07, 2003 at 07:50:56PM +0100, Sylvain LE GALL wrote: > > Hello, > > > > On Fri, Nov 07, 2003 at 08:24:39AM +0100, Sven Luther wrote: > > > On Thu, Nov 06, 2003 at 08:28:05PM +0100, Stefano Zacchiroli wrote: > > > > On Thu, Nov 06, 2003 at 01:05:27AM +0100, Sylvain LE GALL wrote: > > > > > I was just recompiling some of my libs, when i have seen that > > > > > camlidlruntime.h is now standing in /usr/include/ocaml/3.07/camlidl. > > > > > > > > > > I think it is the right place, however, caml install his header in > > > > > /usr/lib/ocaml... > > > > > > > > Thanks for your support to my idea of installing it there :-) > > > > An even more authoritative answer can be found directly in FHS: > > > > > > > > 4.3 /usr/include : Directory for standard include files. > > > > > > > > This is where all of the system's general-use include files for the C > > > > and C++ programming languages should be placed. > > > > > > > > camlidlruntime.h is definitely in this category. > > > > > > > > If noone objects I will close this bug. > > > > > > > > > Any idea ? ( maybe this bug should not go there but to ocaml package > > > > > ). > > > > > > > > Yes: report the bug to the ocaml BTS. Anyway I doubt that anyone is > > > > going to consider this as a bug there too, since noone of the caml team > > > > apparently cares about FHS ... > > > > > > Notice that i definitively have a symlink from /usr/include/caml and > > > ocaml to /usr/lib/ocaml/3.07/caml. > > > > > > Easier to do than creating a separate 3.07 directory in > > > /usr/include/ocaml, and my symlink will probably break your stuff. > > > > What about doing a dir /usr/include/ocaml/3.07/ with ocaml header in it > > and link it to /usr/lib/ocaml/3.07/caml. This won't break anything and > > will permit to do a FHS compliant thing ! > > I did that before, but it is more trouble than it is worth. If we have a > symlink from /usr/include to the right place, where is the problem ? >
Hum... What is happening if someone want to install his header in your simlinked directory ? I know that the problem is symmetric ( ie if someone install something in stdlibdir/caml ). But FHS stats that this must be in include, so there is a total mismatch. Imagine Stefano installs his camlidlruntime.h in your dir, debian package file will have problem removing it ( because it is a link ). I don't see all the problem it could throw, and maybe the one i see is not valid at all... Anyway, i won't obliged anyone to follow FHS nor to follow my advice. It was just a personnal answer that i think could lead some questionning... Kind regard Sylvain LE GALL
