On Wed, Nov 21, 2001 at 12:06:24PM +0100, Florian Weimer wrote:
> Julian Gilbey <[EMAIL PROTECTED]> writes:
>
> > On Wed, Nov 21, 2001 at 11:18:20AM +0100, Florian Weimer wrote:
> > > Is it acceptable to put source files for non-C-related languages
> > > (such as Python, Perl, Ada, Java, and so on) in subdirectories
> > > under /usr/include?
> >
> > What are "source files" in this context?
>
> Complete source files, i.e. you could rebuild the library in question
> from them (with the exception of, for example, parts written in C).
When would one want such things on a system? Only during compilation
of the library in question or other libraries, I presume.
> > Note that /usr/include is generally not for source files, but for
> > header files to be included during compilation.
>
> The GNAT compilation model (GNAT is the Ada compiler) strongly favors
> the presence of both the spec (the .h file) and the body (the .c
> file). For some compilation units (generic units, similar to C++
> templates), complete source code is required, naturally.
Hmm. Would /usr/src be a better location in such situations?
Other thoughts would include using /usr/lib for this purpose.
Also, remember that we only provide files in the .deb's if they are
needed by other packages: source code generally lives in the source
.orig.tar.gz/.diff.gz or .tar.gz files.
Julian
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Julian Gilbey, Dept of Maths, Debian GNU/Linux Developer
Queen Mary, Univ. of London see http://people.debian.org/~jdg/
http://www.maths.qmul.ac.uk/~jdg/ or http://www.debian.org/
Visit http://www.thehungersite.com/ to help feed the hungry
Also: http://www.helpthehungry.org/
