"Jason R. Mastaler" <[EMAIL PROTECTED]> writes: > Stephen Warren <[EMAIL PROTECTED]> wrote on tmda-users: > >> I'm only using TMDA-1.1 on a test user at present, so I have 1.0 and >> 1.1 installed. I (may) need two different configuration files for >> these versions. This patch takes the values of GLOBAL_TMDARC and >> TMDARC and attempts to look for versions suffixed with the TMDA >> branch number (e.g. "1.1") or falls back to the existing name if >> that isn't found. >> >> That way, I can have: >> >> /etc/tmdarc-1.1 >> /etc/tmdarc (for 1.0 - still used for 1.1 if above not present) > > Hmm. This seems like overkill to me.
One thing it does have going for it is that some other apps do similar things. I just ran across one recently that does this, even for the ~/.???rc file, and thought it was kind of nice. > There are ways to handle multiple versions with one config file. > For example, in config: > > from TMDA.Version import TMDA as tmda_version > if tmda_version > '1.1': > # your 1.1.x-only vars here It's nice if the application quietly and correctly handles it, though, rather than making everyone who does require this capability hand-code it. > Most users are only going to be running one or the other anyway. This is, of course, the other side of that issue... how many people really need it, anyhow? The one thing that sways me a little towards doing this is that it is a nice feature if you need it and it quietly does nothing if you don't; that is, it won't cause confusion and tech-support issues if you never need it. > Another option might be to add a '-g' command-line option to > tmda-filter similar to '-c' that overrides the standard location of > the global config file in /etc/tmdarc. And tmda-pending and anything else that reads Defaults... Tim _________________________________________________ tmda-workers mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-workers
