also sprach John Jetmore <[EMAIL PROTECTED]> [2007.08.15.1431 +0200]: > The problem is that before I do this I really want to get a grip on all of > the options, if I'm going to be receiving them from all these possible > locations. This includes defining processing order (I assume CLI trumps ENV > variables trumps cf file, but I haven't thought about it hard yet)
This seems to square exactly with how other programmes do it. > As an example of the latter, consider that in terms of transport, > swaks has three mutually exclusive modes, which can be thought of > as --server for inet sockets (the default), --socket for unix > domain sockets, and --pipe for unix pipes. It should be an error > if any of these are given at the same time, but what if --server > is the default in the cf file and then --socket is given on the > command line? Is that an error, or do I need to sort through the > various layers of options and rectify them? Well, it would be nice if such things only conflicted if they appeared all in the conffile or all on the CLI, so in your example, swaks would start a --socket operation. Cheers, -- .''`. martin f. krafft <[EMAIL PROTECTED]> : :' : proud Debian developer, author, administrator, and user `. `'` http://people.debian.org/~madduck - http://debiansystem.info `- Debian - when you have better things to do than fixing systems "quite frankly, teachers are the only profession that teach our children." - george w. bush
digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/)
