Hi,
While looking through the updates mail, I saw something that sounded
intriguing, hamster-applet. Did a yum info query on it, then thought
I'd install it to have a look. But it wanted to drag in a ridiculous
number of dependencies, most of them devel packages.
Surely a precompiled non-devel
On Tue, 3 Jun 2008 10:56:30 -0400 (EDT), Mike Burger wrote:
On Tue, 2008-06-03 at 09:49 -0400, Mike Burger wrote:
Quite often, those -devel packages have library files included on
which the non-devel package depends. Packages that depend on the
kernel-devel packages spring to mind, but
On Tue, 2008-06-03 at 09:49 -0400, Mike Burger wrote:
Quite often, those -devel packages have library files included on
which the non-devel package depends. Packages that depend on the
kernel-devel packages spring to mind, but many others do, as well.
It rather begs the question though:
On Tue, 2008-06-03 at 09:49 -0400, Mike Burger wrote:
Quite often, those -devel packages have library files included on
which the non-devel package depends. Packages that depend on the
kernel-devel packages spring to mind, but many others do, as well.
It rather begs the question though: why
Michael Schwendt wrote:
I'd wager that xine has libxine statically linked and/or compiled in.
No, libxine.so is just a symlink pointing to the real and versioned
library file in the xine-lib package. This symlink is needed only when
building software -- it's the link that makes the -lxine
On Tue, 3 Jun 2008 09:49:13 -0400 (EDT), Mike Burger wrote:
Hi,
While looking through the updates mail, I saw something that sounded
intriguing, hamster-applet. Did a yum info query on it, then thought
I'd install it to have a look. But it wanted to drag in a ridiculous
number of
On Tue, 03 Jun 2008 16:49:52 +0100, Brian Morrison wrote:
Michael Schwendt wrote:
I'd wager that xine has libxine statically linked and/or compiled in.
No, libxine.so is just a symlink pointing to the real and versioned
library file in the xine-lib package. This symlink is needed only
