On Fri, Aug 15, 2003 at 09:17:15PM +0200, Frank K?ster <[EMAIL PROTECTED]>
wrote:
> - Why not link /usr/etc/ to /etc/qt or the like?
That still wouldn't conform to policy and is an ugly solution anyway. :)
--
Mike Markley <[EMAIL PROTECTED]>
GPG: 0x3B047084 7FC7 0DC0 EF31 DF83 7313 FE2B 77A8 F
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Freitag, 15. August 2003 20:26 schrieb Brian Nelson:
> Dominik Stadler <[EMAIL PROTECTED]> writes:
>
> Nope. You'll need to modify the application source.
thanks for all the help, the hint with QSetting was very helpful. I looked at
the source an
On Fri, Aug 15, 2003 at 09:17:15PM +0200, Frank K?ster <[EMAIL PROTECTED]> wrote:
> - Why not link /usr/etc/ to /etc/qt or the like?
That still wouldn't conform to policy and is an ugly solution anyway. :)
--
Mike Markley <[EMAIL PROTECTED]>
GPG: 0x3B047084 7FC7 0DC0 EF31 DF83 7313 FE2B 77A8 F3
Dominik Stadler <[EMAIL PROTECTED]> schrieb:
[conffile in /usr/etc/settings]
> My question therefore: Is this a case where lintian should allow an
> exception,
> because I have no other way of telling the Qt-Library to search in a
> different directory? Or is it simply not possible?
- How do
Dominik Stadler <[EMAIL PROTECTED]> writes:
>> Why Qt should look in /usr/etc? Configure your program with
>> --sysconfdir=/etc flag and everything should be OK.
>
> Thanks for the hints, but the problem is that the application does not use
> autoconf/automake/configure, but the build-tool qmake.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Freitag, 15. August 2003 20:26 schrieb Brian Nelson:
> Dominik Stadler <[EMAIL PROTECTED]> writes:
>
> Nope. You'll need to modify the application source.
thanks for all the help, the hint with QSetting was very helpful. I looked at
the source an
Dominik Stadler <[EMAIL PROTECTED]> writes:
> Hi,
>
> I started working on a debian-package. The application uses the Qt-Library as
> basis (no KDE). During startup, the application looks in a directory
> "/usr/etc/settings/" for system-wide settings for the application. This is
> not coded in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> Why Qt should look in /usr/etc? Configure your program with
> --sysconfdir=/etc flag and everything should be OK.
Thanks for the hints, but the problem is that the application does not use
autoconf/automake/configure, but the build-tool qmake. Is
On Fri, Aug 15, 2003 at 06:42:03PM +0200, Dominik Stadler wrote:
> I started working on a debian-package. The application uses the Qt-Library as
> basis (no KDE). During startup, the application looks in a directory
> "/usr/etc/settings/" for system-wide settings for the application. This is
> n
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I started working on a debian-package. The application uses the Qt-Library as
basis (no KDE). During startup, the application looks in a directory
"/usr/etc/settings/" for system-wide settings for the application. This is
not coded inside the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> Why Qt should look in /usr/etc? Configure your program with
> --sysconfdir=/etc flag and everything should be OK.
Thanks for the hints, but the problem is that the application does not use
autoconf/automake/configure, but the build-tool qmake. Is
On Fri, Aug 15, 2003 at 06:42:03PM +0200, Dominik Stadler wrote:
> I started working on a debian-package. The application uses the Qt-Library as
> basis (no KDE). During startup, the application looks in a directory
> "/usr/etc/settings/" for system-wide settings for the application. This is
> n
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I started working on a debian-package. The application uses the Qt-Library as
basis (no KDE). During startup, the application looks in a directory
"/usr/etc/settings/" for system-wide settings for the application. This is
not coded inside the
13 matches
Mail list logo
