Roman Neuhauser <[EMAIL PROTECTED]> writes:
> TMDA cannot be configured to use a system-wide configfile other than
> /etc/tmdarc.
That's correct.
> this path (and I think a few others) is hardcoded all over the
> thing. Is there any special reason for this?
I assume you are talking about ~/.tmda/config, otherwise I'm not sure
what you mean. Well, it's a chicken and egg problem---how can we read
the user's configuration file to determine where his configuration
file is located so we can read it? We have to choose a default
location.
You can override ~/.tmda/config with tmda-filter's `-c' option. See
`tmda-filter -h' for more info. Also, if $TMDARC is set in the
environment, tmda-filter will assume this is the location of the
user's configuration file.
I don't have a command-line option or environment variable for
/etc/tmdarc, but these could be added if necessary. Why do you need it
in a different location?
> I know, the docs say TMDA is written to run from the source
> directory (doesn't need to be properly installed), but again: is
> there any special reson for this?
The bin/tmda-* programs needs to be able to find the TMDA modules in
../TMDA/. However, it's possible to make symlinks from a standard
location like /usr/local/bin/ back to the /usr/src/tmda/bin/tmda-*
programs.
The packaged installations like RPM and *BSD ports get around this by
installing the TMDA modules directly into Python's sys.path (e.g,
/usr/local/lib/python2.2/site-packages/TMDA/).
> I'm asking about this because of the FreeBSD port. I know TMDA
> doesn't put anything in /etc by itself, but ports are supposed to be
> ${PREFIX}-clean, and the rest of what's installed by
> /usr/ports/mail/tmda/Makefile is put under /usr/local...
I don't understand what you are asking here, can you elaborate?
_____________________________________________
tmda-users mailing list ([EMAIL PROTECTED])
http://tmda.net/lists/listinfo/tmda-users
