Hello, Glus. First of all, autoconf works at build time, not install time. A particular system, on which you install the software, may have habits different from build system. Second, autoconf relies on development tools, which may be not available at install time. And last, but not least, autoconf is explicitly designed to detect only features, the build depends upon. Briefly speaking, autoconf is not a right tool to detect system administrative environment. Typically, application packager makes separate packages for every particular system he supports. Best regards, -- Konstantin Andreev, software engineer. Swemel JSC On Tue, 15 Dec 2009, Glus Xof wrote:
Yesterday, I wrote,I understand.,, but what happens about /etc/init.d shell scripts (I mean the ones which start, stop & restart servers) ? Would be possible to get more info about the way of manage them ?But, this silence starts to make me think. Maybe, you want to tell me that these scripts are also the task of the one who installs the server... doesn't it ? Glus
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ Autoconf mailing list Autoconf@xxxxxxx http://lists.gnu.org/mailman/listinfo/autoconf
