[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: /package support
|
From: |
Paul Eggert |
|
Subject: |
Re: /package support |
|
Date: |
Fri, 13 Dec 2002 01:05:32 -0800 (PST) |
> Date: Thu, 12 Dec 2002 19:49:08 +0100
> From: Stefan Karrmann <address@hidden>
> User-Agent: Mutt/1.3.27i
>
> Does autoconf support /package (see http://cr.yp.to/slashpackage.html)?
That depend on what you mean by "support". It doesn't prohibit
/package, but it doesn't go out of its way to help either.
Suppose, for example, that an Autoconf-generated "configure" finds a
package on the installer's machine at compile-time, which is not
available on the run-time machine, and is not explicitly listed as a
run-time dependency. The program won't work. Is that Autoconf's
fault? Should Autoconf help out on this? As far as I know, nobody
has really thought about these issues. Someone who likes /package
will have to volunteer to do the hard slogging, I'm afraid.