On Fri, Jun 09, 2000 at 02:57:21AM +0200, Peter Eisentraut wrote:
> I'd find it *immensely* helpful if configure also looked for a config.site
> (or an equivalent file of different name) in the current directory.
How about config.pkg? This file will contain options specific to
a particular package, whereas config.site is for options that
are global to all packages.
> This
> would especially be helpful to developers and semi-developers who
> frequently update via CVS and re-configure all the time.
And for packages like Amanda, which is a network application with
a zillion config options. Many (but not all) of these options
should be in a site-wide policy file, but, because they're
specific to the one package, they don't belong in config.site.
I had patches for this at one point. I'll see if I can dig them
up.
--
| | /\
|-_|/ > Eric Siegerman, Toronto, Ont. [EMAIL PROTECTED]
| | /
to me, Charlie Brown represented the courage to be sincere in the face of
ridicule. he was NOT a loser.
thank you, Mr. Schulz.
- Robert C. Mayo
