Sorry for speaking for you, Roman; If I'm wrong on any of this, please
don't hesitate to correct me.
On Fri, 24 Jan 2003, Jason R. Mastaler wrote:
> > 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.
I think he means /etc/tmdarc. The user's config file location can be
changed in /etc/tmdarc, but how do you change the location of the
/etc/tmdarc file? This should probably be an install- or compile-time
option.
> > 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?
I think he means that when a FreeBSD port is installed in a certian
location (or prefix), such as /usr/local (instead of / or /usr), it makes
things a lot "cleaner" to have everything at the same level... programs
go in /usr/local/bin, libs go in /usr/local/lib, configs go in
/usr/local/etc, and so on. Nothing is "supposed to be" below whatever
${PREFIX} the port maintainer or user picks. Therefore forcing tmda's
systemwide config to /etc/tmdarc is undesirable.
Without arguing whether or not this is a Good Thing, that is what FreeBSD
ports (and maybe other port/package systems, I can't speak for them) like
to do.
Jim Ramsay
_____________________________________________
tmda-users mailing list ([EMAIL PROTECTED])
http://tmda.net/lists/listinfo/tmda-users
