--4bRzO86E/ozDv8r1
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, Feb 28, 2002 at 11:41:38PM +0100, aleXXX wrote:
> On Thursday 28 February 2002 11:01, Thomas Zander wrote:
> >
> > He explained privately; the /etc/lisarc is hard-coded; that is the prob=
lem.
>=20
> I intentionally made the path hard-coded.
> In former versions lisa tried to look for the config file in the kde conf=
ig=20
> dirs, this lead to many problems, since the user has to take care that li=
sa=20
> is started (at boot time). With the former scheme there were options whet=
her=20
> lisa should look in the kde-1-config-dirs (i.e. $KDEDIR/share/config and=
=20
> ~/.kde/share/config I think)  or in kde-2-config-dirs (via kde-config) or=
 in=20
> unix-style config dirs (i.e. /etc/lisarc and ~/.lisarc). Since there were=
 to=20
> many points where things could go wrong I decided to support only /etc/li=
sarc=20
> and ~/.lisarc.
> And since lisa doesn't link any Qt/KDE lib, it can't use the KDE classes=
=20
> therefor.

Understood; that is not my problem.


> I still don't understand the problem.

Well the problem is that I want a mimimum maintainance software system. In =
other=20
words I don't like to have a config path hardcoded in 5 places in the class=
es.
I'd much rather like a header file #define or static where the path is. It =
simply
makes maintainance easier.

I don't know anything about the problems you describe above; I simply belie=
ve you
that the path has to be hardcoded; but for example debian will probably put=
 the=20
file somewhere else, lets allow them to do that with a simple patch that up=
dates
1 string in 1 header file. So we don't get bug reports that are created by =
the
overlooking of 1 of the 5 strings that are all the same.

--=20
Thomas Zander                                            zander@earthling.n=
et
The only thing worse than failure is the fear of trying something new

--4bRzO86E/ozDv8r1
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE8fqOiCojCW6H2z/QRAslDAJ94Psea0SYQYmrpoda4jT0r9SUMSACgwIJm
kR+W4qGIW21WfGFvRqzvUQw=
=LuSf
-----END PGP SIGNATURE-----

--4bRzO86E/ozDv8r1--