[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

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 method to this madness?
>
> It seems to me that it would be easier to use the environment for
> standard config variables (such as MIRROR, NONFREE, etc, etc)
>
> which_deb, for instance, takes the config variables of MIRROR and
> CODENAME as its first two arguments, followed by a package name and
> output format (which I believe should be arguments).

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.

P.S. Are you subscribed to the list or should we continue to CC you?

Attachment: signature.asc
Description: This is a digitally signed message part.


Reply to: