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
Title: ìì´ ë°°ì°ë ì¦ê±°ìê³¼ 기ì¨ì´ ê°ë¬¼ì²ë¼ í르ë íë³µí SES 보기!
ìì´ ë°°ì°ë ì¦ê±°ìê³¼ 기ì¨ì´ ê°ë¬¼ì²ë¼ í르ë íë³µí
SES 보기!
SESë 24ìê° Tutorì í¨ê» ìííë 기ìì ìì´ì°ìì
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,
Hi all,
OK, there wasn't very much response from the HTTP daemon maintainers to
either me or this list (actually none at all)...
But there's at least on package (caudium) which already Provides:
httpd-cgi...
How should I proceed now?
File bugs against the other HTTPds? Make an official policy-pr
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
Processing commands for [EMAIL PROTECTED]:
> retitle 120418 [PROPOSAL] CPU extension code
Bug#120418: cc: Michel LESPINASSE <[EMAIL PROTECTED]>,Robert Stone <[EMAIL
PROTECTED]>,Eduard Bloch <[EMAIL PROTECTED]>,Adam C Powell IV <[EMAIL
PROTECTED]>,Dirk Eddelbuettel <[EMAIL PROTECTED]>,[EMAIL PROT
AALWAY, TOUT LE LOGICIEL POUR LA COMMUNAUTE DU NET
LA LETTRE D'INFO du 21 novembre 2001
http://www.aalway.net/index_assur201101.php
Bonjour,
* 30% de remise sur tous nos logi
13 matches
Mail list logo
