Environment variables vs. command-line arguments

It seems there is quite a hodge-podge of calling conventions for passing config variables to the scripts in the tools/ directory. Several scripts take command line arguments; others use environment variables. Some use both. Is there a method to this madness? It seems to me that it would be

Re: Environment variables vs. command-line arguments

Hi Jonathan, On Thu, Feb 05, 2009 at 09:57:31AM -0600, Jonathan Hall wrote: > It seems there is quite a hodge-podge of calling conventions for passing > config variables to the scripts in the tools/ directory. Several > scripts take command line arguments; others use environment variables.

Re: Environment variables vs. command-line arguments

On Thursday 05 February 2009, Jonathan Hall wrote: > It seems there is quite a hodge-podge of calling conventions for > passing config variables to the scripts in the tools/ directory. > Several scripts take command line arguments; others use environment > variables. Some use both. > > Is there a

Re: Environment variables vs. command-line arguments

I'm on the list. I agree. MIRROR should definitely not be passed in as an argument as "local" can have a different mirror path (LOCALDEBS) from the main mirror (MIRROR). which_deb should support that. That's exactly what I was running into... trying to expand to support "other" components,

Re: Environment variables vs. command-line arguments

Do you prefer to have cleanup patches submitted to the list, or as wishlist bugs? Patches / suggestions welcome to start cleaning things up, although obviously major changes will have to be post-lenny now.. -- Inbound and outbound email scanned for spam and viruses by the DoubleCheck Em