Chris Waters <[EMAIL PROTECTED]> writes:
> On Wed, Nov 21, 2001 at 12:38:55PM +0100, Wichert Akkerman wrote:
>
> > Quoting from section 4.3 of the FHS 2.1:
>
> Which in turn suggests the proper solution: ask on the FHS lists, and
> maybe on ada/gnat developer lists.
I think I used the official
Wichert Akkerman <[EMAIL PROTECTED]> writes:
> Quoting from section 4.3 of the FHS 2.1:
>
>
> 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.
A, tha
Previously Matthew Palmer wrote:
> There is precedent (kind of), g++ uses /usr/include/g++, so why not
> /usr/include/{gnat|ada}?
c++ is a a C derivative, and the FHS explicitly limits /usr/include
to C. If you want to change the FHS bring this up on the fhs-discuss
list first.
Wichert.
--
__
On Wed, 21 Nov 2001, Chris Waters wrote:
> > How about using /usr/share/ada instead?
>
> Speaking for myself, yuck! I'd much prefer to use /usr/include for
> this. But I'm not an ada expert, and I don't know what the historical
> precedent (if any) is. Maybe we should find out how it's _suppos
On Wed, Nov 21, 2001 at 12:38:55PM +0100, Wichert Akkerman wrote:
> Quoting from section 4.3 of the FHS 2.1:
Which in turn suggests the proper solution: ask on the FHS lists, and
maybe on ada/gnat developer lists. Try to find an answer that applies
to everyone, not just to Debian, and I suspect
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
Previously Florian Weimer wrote:
> What about the Ada case? GNAT pretty much requires that complete
> source code is present for all compilation units at compilation (and
> binding/linking) time. And package specs are very similar to C header
> files, at least with the GNAT compilation model.
Qu
Wichert Akkerman <[EMAIL PROTECTED]> writes:
> Previously 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?
>
> I'ld say no. Those languages don't use include files,
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" i
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? Note that /usr/include is
generally no
Previously 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?
I'ld say no. Those languages don't use include files, they use
libraries.
Wichert.
--
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?
It does make some sense, but I don't like this idea. Policy doesn't
seem to cover this issue.
--
Florian Weimer[EMAIL PROTECTED
12 matches
Mail list logo
