On 04 Feb 2000 01:27:14 CST, the world broke into rejoicing as
Rob Browning <[EMAIL PROTECTED]> said:
> Christopher Browne <[EMAIL PROTECTED]> writes:
>
> > Would it be an unreasonable idea to set up a set of default locations
> > in which GnuCash should look for configuration, falling back as needed?
>
> I'm kind of skittish about searching for *important* directories like
> this at runtime rather than embedding them at build time.
>
> I came across this recently when dealing with emacs' detection of the
> mail spool directory. My assumption in this case is that when you're
> building a particular program for a given machine, you know where the
> mail spool is. If another directory that looks like a mail spool
> happens to pop up later (perhaps because some other program's
> installation process does the "wrong thing"(TM)), you shouldn't just
> silently change behaviors and start using the new directory. Among
> other things, this could be a security hole.
Counterpoint:
What if GnuCash is being deployed as an RPM or .deb package? In that
case, the user is not building the package for a "given machine."
If we leave the options open, this is supportive even of users that
set up fairly peculiar system configurations.
It is supportive of responding to questions via: "OK. We can solve your
problem by adding the following line to your .bashrc file."
I'm not feeling dogmatic about it, though.
--
"what would we do without C? we would have PASAL, BASI, OBOL, and
Ommon Lisp." -- #Erik
[EMAIL PROTECTED] - <http://www.ntlug.org/~cbbrowne/lsf.html>
--
Gnucash Developer's List
To unsubscribe send empty email to: [EMAIL PROTECTED]
