tag 500037 +confirmed
tag 500037 +wontfix
thanks
Hi,
Stefano Zacchiroli wrote:
> Package: latex-make
> Version: 2.1.11-2
> Severity: normal
> File: /usr/include/LaTeX.mk
>
> According to my reading of FHS, latex-make should not install makefile
> snippets under /usr/include/, as that directory is specifically meant
> for includes for the C programming language.
I use this directory because GNU Make uses it. From its documentation
(about includes)
-------------
If the specified name does not start with a slash, and the file is
not found in the current directory, several other directories are
searched. First, any directories you have specified with the `-I' or
`--include-dir' option are searched (*note Summary of Options: Options
Summary.). Then the following directories (if they exist) are
searched, in this order: `PREFIX/include' (normally `/usr/local/include'
(1)) `/usr/gnu/include', `/usr/local/include', `/usr/include'.
-------------
I do not want that debian users of LaTeX-Make have to hardcode the
path into LaTeX.mk file. It would cause to much pain when working
on LaTeX documents on several plate-forms shared with svn. For example,
LaTeX.mk will not have the same absolute PATH on Debian/MacOSX/
local installation,...
So, I need to use one of the automatically searched path by GNUMake.
/usr/local/* cannot be used. Would /usr/gnu/include be better ? I do
not think so (/usr/gnu is not cited at all in the FHS).
> Here is a relevant quote from
> /usr/share/doc/debian-policy/fhs/fhs-2.3.txt.gz , Chapter 4:
>
>
> -------------------------------------------------------------------------------
>
> /usr/include : Directory for standard include files.
>
> Purpose
>
> This is where all of the system's general-use include files for the C
> programming language should be placed.
>
>
> -------------------------------------------------------------------------------
>
> It does not annoy me to have stuff not related to the C programming
> language there. Still, *if* it is allowed to have non-C stuff there I
> would like it to be properly stated, so that others can rely on that
> (new) semantics.
This paragraph does not forbid to install include files for other languages.
For example, C++ header files are also here. And also GNUstep header files
(GNU Objective-C/C++). Both are derivative language from the C language but
they cannot be used in a C program. Make also has its (declarative) language
that can be quite complex (see LaTeX.mk ;-) ). So, this location is not fully
inadequate from my point of view.
I fully agree that using a separate directory would be better.
However :
- GNUMake uses this directory since a very long time
- other GNUMake directories seem worst (/usr/local/* or /usr/gnu/include)
- requiring LaTeX-Make users to use a full path is not an option
(as I said before, lots of use cases broken)
So, I wont fix this bug for now.
If GNUMake searches in another (better) directory, then I will change
LaTeX-Make to use it.
If you have free time, you can ask upstream GNUMake (or the Debian 'make'
package) to add such another directory (/usr/share/make/include ?)
It will probably be quicker than waiting I find some free time to do
it myself.
Regards,
Vincent
--
Vincent Danjean GPG key ID 0x9D025E87 [EMAIL PROTECTED]
GPG key fingerprint: FC95 08A6 854D DB48 4B9A 8A94 0BF7 7867 9D02 5E87
Unofficial pacakges: http://www-id.imag.fr/~danjean/deb.html#package
APT repo: deb http://perso.debian.org/~vdanjean/debian unstable main
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
