Dear Sune! Am Mittwoch, den 19.12.2007, 23:43 +0100 schrieb Sune Vuorela: > I have read the discussion in the bug report. If it is anywhere else, please > point to it instead of playing smart-ass.
That applies to everyone: I don't like the tone of the recent emails and would be glad if we could all calm down and keep the discussion at a technical level, so we can spend our time on working on Debian and not flaming each other. > From the fhs: > /usr/include : Directory for standard include files. > /usr/lib : Libraries for programming and packages > > mpi.h surely only fits in first category. mpi.h is provided in /usr/include/mpi via update-alternatives, as every other include file needed by an MPI implementation is, so I do not see the problem here. I don't find a reference in the policy that states that one is not allowed to symlink to where the files reside in the filesystem. Actually, all packages using update-alternatives I looked at so far put their stuff in /usr/lib/package. If that's wrong, we can correct that. But from what I saw this is common practice. mpich even has files in /usr/lib/mpich/bin. IANADD, so I may be wrong and looked at broken packages. Could you please give me some insight how a solution would look like in your eyes? Thanks in advance! Best regards Manuel
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil