Re: KDE debs
-----BEGIN PGP SIGNED MESSAGE-----
On Fri, 5 Feb 1999 MallarJ@aol.com wrote:
> Curious about something...
> I didn't know there was a qt-1.42.deb available, so yesterday I downloaded the
> qt source and compiled my own. I have libc126.96.36.199t - do I need to upgrade to
> a new version to get them to work? I tried some of the example code that
> comes with the qt source, and they seemed to work fine...
It should work fine. What I've occasionally done is download the source
to a package from the Debian ftp site (including the .diff and .dsc file)
and built my own local package. There's really nothing in the Qt 1.42
sources that would require you to have a specific libc version; it's just
that that's the version that the maintainer built their package against.
For example, I most recently did this with xfstt, the X TrueType font
server. I was running hamm at the time, but the slink xfstt was
supposedly much nicer. But I didn't have the slink libc, and I didn't
ywant it. So I got the source to the slink xfstt package and built it on
my hamm system. As far as dpkg and dselect are concerned, I have the
slink version of the package, and I satisfy all the dependencies.
Since you've got the Qt sources already, you could just get the .diff and
.dsc file from the Debian site, and build yourself a hamm (or slink, or
whatever) package that would satisfy the dependencies of the current KDE
packages. Unfortunately, I don't remember the procedures off-hand, and I
don't have access to my machine right now to find out. Check out the
"source packages" section of the Debian packaging documentation on the web
PGP public key available at
or by 'finger -l email@example.com'
This message was composed in a 100% Microsoft free environment.
-----BEGIN PGP SIGNATURE-----
-----END PGP SIGNATURE-----