4:03 p.m.
It seems that mplayer's dependencies on RPM Fusion include (perhaps
indirectly) mencoder, samba-common and samba-winbind. Are these really
necessary? This does matter on a netbook with 4G SSD.
Andras
9:10 p.m.
Michael Schwendt wrote:
On Tue, 4 Nov 2008 01:25:29 +0100, Andras Simon wrote:
> In other words, my question is not about whether mplayer really
> depends on those other packages, but whether it should depend on them.
> And I still think that downloading the rpm file will not answer this.
> (I may very well be wrong, of course.) Browsing mplayerhq.hu
> may. Or asking about it here.
Well, with the downloaded pkg I showed that /usr/bin/mplayer actually is
linked against the Samba Client library. That library would not be
available during compilation if it weren't pulled in as a build
requirement of some sort. The pkg could also contain documentation
files which mention the SMB features in mplayer. ;)
Btw, RPM Fusion runs a list for its users:
http://lists.rpmfusion.org/mailman/listinfo/rpmfusion-users
If you ever build mplayer for the sources, you'll see that it has about
a hundred configuration options, most of which a "normal" user doesn't
need or want. Note that I said configuration "options", not
"requirements" (big difference). Looks like the package maintainer has
chosen to include them all, including the kitchen sink. But what else
could he do? Definitely a case where you might be better off rolling
your own version.
Regards,
John
6:16 a.m.
On 11/4/08, john wendel <jwendel10(a)comcast.net> wrote:
If you ever build mplayer for the sources, you'll see that it has
about
a hundred configuration options, most of which a "normal" user doesn't
need or want. Note that I said configuration "options", not
"requirements" (big difference). Looks like the package maintainer has
chosen to include them all, including the kitchen sink. But what else
could he do?
Yes, this is a problem not just with mplayer but with a lot of
packages. For example, ghostscript used to require the whole CUPS
cruft, even if you never planned to actually print something.
Definitely a case where you might be better off
rolling
your own version.
Right, except that then you have to install a lot of development
packages... and enter dependency hell through another gate. Besides,
large-scale compilation on a netbook with a small SSD is something I'd
love to get by without.
Andras
7:11 p.m.
On Tue, 4 Nov 2008 01:25:29 +0100, Andras Simon wrote:
In other words, my question is not about whether mplayer really
depends on those other packages, but whether it should depend on them.
And I still think that downloading the rpm file will not answer this.
(I may very well be wrong, of course.) Browsing mplayerhq.hu
may. Or asking about it here.
Well, with the downloaded pkg I showed that /usr/bin/mplayer actually is
linked against the Samba Client library. That library would not be
available during compilation if it weren't pulled in as a build
requirement of some sort. The pkg could also contain documentation
files which mention the SMB features in mplayer. ;)
Btw, RPM Fusion runs a list for its users:
http://lists.rpmfusion.org/mailman/listinfo/rpmfusion-users
6:34 p.m.
To partly answer my own question... probably this is the reason for
the dependency of mplayer on samba:
1. Input layer, supported devices, methods:
[...]
- SMB - file access over samba (experimental)
http://www.mplayerhq.hu/DOCS/tech/formats.txt
6:25 p.m.
On 11/4/08, Michael Schwendt <mschwendt(a)gmail.com> wrote:
On Tue, 4 Nov 2008 00:08:06 +0100, Andras Simon wrote:
> On 11/3/08, Michael Schwendt <mschwendt(a)gmail.com> wrote:
> > On Mon, 3 Nov 2008 23:03:45 +0100, Andras Simon wrote:
> >
> >> It seems that mplayer's dependencies on RPM Fusion include (perhaps
> >> indirectly) mencoder, samba-common and samba-winbind. Are these really
> >> necessary? This does matter on a netbook with 4G SSD.
> >
> > It "seems"? No, it's a fact. You can demonstrate it easily.
> >
> > $ rpm -qpR mplayer-1.0-0.97.20080903svn.fc9.1.i386.rpm|grep smb
> > libsmbclient.so.0
>
> You can, if you've updated mplayer already. I haven't, because I
> thought I'd ask first.
??
$ rpm -q mplayer
package mplayer is not installed
You, too, can download the package with your favourite browser or
yumdownloader to examine it. No updating of installed packages is
necessary.
You're right. And I missed the point because I missed the '.rpm' at the end
of the package name above (i.e. I thought you were querying an
installed package, not the rpm file) - sorry about that. But the
reason for my temporary blindness is that I wasn't suspecting a
trivial packaging bug. By "really necessary" I meant (and I realize
that that's not at all obvious) whether the capability that, say
samba-common provides, should really be compiled in mplayer. Or, in
the case of mencoder, which, unlike samba-*, is also an RPM Fusion
package, whether the needed libraries could be separated from mencoder
and both mplayer and mencoder be made dependent on a new package that
contains those libs.
In other words, my question is not about whether mplayer really
depends on those other packages, but whether it should depend on them.
And I still think that downloading the rpm file will not answer this.
(I may very well be wrong, of course.) Browsing mplayerhq.hu
may. Or asking about it here.
Andras
5:32 p.m.
On Tue, 4 Nov 2008 00:08:06 +0100, Andras Simon wrote:
On 11/3/08, Michael Schwendt <mschwendt(a)gmail.com> wrote:
> On Mon, 3 Nov 2008 23:03:45 +0100, Andras Simon wrote:
>
>> It seems that mplayer's dependencies on RPM Fusion include (perhaps
>> indirectly) mencoder, samba-common and samba-winbind. Are these really
>> necessary? This does matter on a netbook with 4G SSD.
>
> It "seems"? No, it's a fact. You can demonstrate it easily.
>
> $ rpm -qpR mplayer-1.0-0.97.20080903svn.fc9.1.i386.rpm|grep smb
> libsmbclient.so.0
You can, if you've updated mplayer already. I haven't, because I
thought I'd ask first.
??
$ rpm -q mplayer
package mplayer is not installed
You, too, can download the package with your favourite browser or
yumdownloader to examine it. No updating of installed packages is
necessary.
> And with an extracted /usr/bin/mplayer:
>
> $ ldd mplayer|grep smb
> libsmbclient.so.0 => /usr/lib/libsmbclient.so.0 (0x065a3000)
Ditto.
Same here. You can extract files from an uninstalled RPM package.
> Now, to answer your question, complete the rest of the exercise
yourself
> and find out where/how exactly the smbclient lib is used inside mplayer.
It's not exactly what I'd call an answer, but thanks anyway.
Why not? The main mplayer currently is linked with the Samba Client
library. Either that's needed for a some feature, or it's a bug.
Find out what's the case.
5:08 p.m.
On 11/3/08, Michael Schwendt <mschwendt(a)gmail.com> wrote:
On Mon, 3 Nov 2008 23:03:45 +0100, Andras Simon wrote:
> It seems that mplayer's dependencies on RPM Fusion include (perhaps
> indirectly) mencoder, samba-common and samba-winbind. Are these really
> necessary? This does matter on a netbook with 4G SSD.
It "seems"? No, it's a fact. You can demonstrate it easily.
$ rpm -qpR mplayer-1.0-0.97.20080903svn.fc9.1.i386.rpm|grep smb
libsmbclient.so.0
You can, if you've updated mplayer already. I haven't, because I
thought I'd ask first.
And with an extracted /usr/bin/mplayer:
$ ldd mplayer|grep smb
libsmbclient.so.0 => /usr/lib/libsmbclient.so.0 (0x065a3000)
Ditto.
Now, to answer your question, complete the rest of the exercise
yourself
and find out where/how exactly the smbclient lib is used inside mplayer.
It's not exactly what I'd call an answer, but thanks anyway.
Andras
4:42 p.m.
On Mon, 3 Nov 2008 23:03:45 +0100, Andras Simon wrote:
It seems that mplayer's dependencies on RPM Fusion include
(perhaps
indirectly) mencoder, samba-common and samba-winbind. Are these really
necessary? This does matter on a netbook with 4G SSD.
It "seems"? No, it's a fact. You can demonstrate it easily.
$ rpm -qpR mplayer-1.0-0.97.20080903svn.fc9.1.i386.rpm|grep smb
libsmbclient.so.0
And with an extracted /usr/bin/mplayer:
$ ldd mplayer|grep smb
libsmbclient.so.0 => /usr/lib/libsmbclient.so.0 (0x065a3000)
Now, to answer your question, complete the rest of the exercise yourself
and find out where/how exactly the smbclient lib is used inside mplayer.
5683
days inactive
5684
days old
8 comments
3 participants
participants (3)
-
Andras Simon -
John Wendel -
Michael Schwendt