# [EMAIL PROTECTED] / 2003-01-24 13:03:19 -0700:
> 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.
Actually, I meant /etc/tofmipd - among others. A few hits of
`grep -FIHnr @@PREFIX@@ .|sed -E 's/@@PREFIX@@//g'`:
./TMDA/Auth.py:68: authfile = '/etc/tofmipd'
./TMDA/Defaults.py:66:GLOBAL_TMDARC = '/etc/tmdarc'
./TMDA/Util.py:719: searchdirs.append('/etc/tmda/')
./contrib/cgi/Authenticate.py:112: FN = "/etc/tmda-cgi"
> > 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/).
why does TMDA itself not do it this way?
--
If you cc me or remove the list(s) completely I'll most likely ignore
your message. see http://www.eyrie.org./~eagle/faqs/questions.html
_____________________________________________
tmda-users mailing list ([EMAIL PROTECTED])
http://tmda.net/lists/listinfo/tmda-users
