delorie.com/archives/browse.cgi | search |
X-Authentication-Warning: | delorie.com: mailnull set sender to djgpp-workers-bounces using -f |
To: | "Tim Van Holder" <tim DOT van DOT holder AT pandora DOT be> |
CC: | djgpp-workers AT delorie DOT com |
In-reply-to: | <000b01c1c808$3f562bb0$8b5f77d5@zastaixp> |
(tim DOT van DOT holder AT pandora DOT be) | |
Subject: | Re: autoconf / config.site |
References: | <000b01c1c808$3f562bb0$8b5f77d5 AT zastaixp> |
Message-Id: | <E16k6yH-0007HF-00@fencepost.gnu.org> |
From: | Eli Zaretskii <eliz AT gnu DOT org> |
Date: | Sun, 10 Mar 2002 12:18:57 -0500 |
Reply-To: | djgpp-workers AT delorie DOT com |
Errors-To: | nobody AT delorie DOT com |
X-Mailing-List: | djgpp-workers AT delorie DOT com |
X-Unsubscribes-To: | listserv AT delorie DOT com |
> From: "Tim Van Holder" <tim DOT van DOT holder AT pandora DOT be> > Date: Sun, 10 Mar 2002 08:50:28 +0100 > > I'd also like to discuss the possibility of having > config.site in its own mini-package. It's now > distributed with both bash and autoconf, and it does not > make sense to update one set of packages whenever the > other set changes. Having it in its own package would > allow it to have its own lifecycle. How about if the config.site distributed with Bash will source the one distributed with Autoconf, if it finds it in some specific directory, like %DJDIR%/share/autoconf? Then you could put on the file distributed with Autoconf only those things Autoconf needs.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |