[ATrpms-users] new mythtv packages increased dependencies

[Bas Hulsken]

>From: Axel Thimm <Axel.Thimm at ATrpms.net>
>Reply-To: ATrpms user list <atrpms-users at ATrpms.net>
>To: Bas Hulsken <bhulsken at hotmail.com>
>CC: ATrpms user list <atrpms-users at ATrpms.net>
>Subject: Re: new mythtv packages increased dependencies
>Date: Sun, 29 Jul 2007 14:30:54 +0200
>
>On Sun, Jul 29, 2007 at 11:40:26AM +0000, Bas Hulsken wrote:
> > Hi Axel,
> >
> > not sure if this is a bug, or a feature, but just thought I'd report 
>this.
> >
> > I've been using the atrpms mythtv packages for more than a year now, I 
>run
> > a headless backend, and a macmini ppc frontend. Up to now, only
> > mythtv-backend (plus a few dependencies) was installed on the headless
> > backend server, and only mythtv-frontend (plus a few dependencies) was
> > installed on the frontend.
> >
> > But as of the last update, this no longer works, I need to install both 
>the
> > frontend, backend, and all plugins on both the backend and the frontend.
>
>Can you outline why? The opposite should be the case.
unsure why, I just ran yum update, the 102 extra dependencies were the 
result. However, reading the rest of your mail, I did some testing, and I 
think I understand now what happened:

The mythtv package I have installed now (after upgrading the backend to your 
new mythtv packages) contains no files, so I'm assuming it's some sort of 
meta package. it seems to require these packages:
mythtv-docs
mythtv-backend
mythtv-frontend
mythtv-setup
perl-MythTV
qt-MySQL
mythplugins
myththemes
mysql-server
mysql
xmltv
wget >= 1.9.1
rpmlib(VersionedDependencies) <= 3.0.3-1
rpmlib(PayloadFilesHavePrefix) <= 4.0-1
rpmlib(CompressedFileNames) <= 3.0.4-1

but before the update, mythtv wasn't a meta package, it included the 
/usr/share/doc part mythtv. And it was a required package for at least 
mythtv-frontend (I can only check this on the frontend now, since the 
backend has already been updated). So for the old mythtv packages mythtv was 
not a meta package, but was a required package for mythtv-frontend, it  
didn't have any dependencies, only:
/bin/bash
/bin/sh
rpmlib(CompressedFileNames) <= 3.0.4-1
rpmlib(PayloadFilesHavePrefix) <= 4.0-1

So I'm pretty sure, that what happend is the following:
mythtv gets updated, it was previously a package with no dependencies, only 
including the mythtv docs, but it gets updated to a meta package, which has 
as dependencies the entire mythtv suite. So all these dependencies will be 
installed. Leading to the 102 extra packages installed in my case.

So to summarize, I think it's neither a bug in the dependencies, nor a user 
error. It's just caused by the fact that the 'mythtv' package name is used 
for the meta package in the new version of the rpms, and for the doc package 
in the old version. So this won't bite you if you do a new install, but I'm 
guessing all users doing a 'yum update' will have this issue. Perhaps the 
apt way of doing things avoids this issue...

well.. that's my best guess anyway.

thanks for the help!
best regards,
Bas



>
> > I've only updated the backend so far, and this resulted in 102
> > (one-hundred-and-two) extra packages installed to meet all
> > dependencies! Is this really necessary?
>
>No, certainly not, something else is amiss.
>
> > And if so, what's the use of all the separate mythtv-* rpms anyway,
> > why not just one big rpm?
>
>Well, you're contradicting your initial request: If all were in one
>rpm, then that rpm would need to pull in *all* dependencies. If it's
>split then everyone can pull in what he really needs and only the
>dependencies needed for that subset would get pulled in.
>
> > well.. I'm afraid I sound a bit like a nag, I'm very grateful for
> > your packages, it's a lot more convenient than building from source
> > myself. I'm just a bit shocked to find out that the mythtv suite now
> > has almost as many dependencies as a lean fc6 install.
>
>mythtv-suite is not intended for installing just mythtv-backend, it
>implies really everything. mythtv-suite alwys had a ton of depdencies,
>this didn't change.
>
>This is either a bug in the depdencies of the myth packages, or a user
>error. FWIW I installed mythtv-backend on a minimal FC6/i386 system
>and it seems to behave properly:
>
>The following NEW packages will be installed:
>Glide3 Glide3-libGL alsa-lib arts audiofile audit-libs-python esound
>fontconfig freetype glib2 jack-audio-connection-kit lcms libICE libSM
>libX11 libXau libXcursor libXdmcp libXext libXfixes libXft libXinerama
>libXmu libXrandr libXrender libXt libXv libXvMC libXxf86vm libavc1394
>libfreebob libiec61883 libjpeg libmng libmp3lame0 libmyth-0.21_0
>libmythavcodec-0.21_0 libmythavformat-0.21_0 libmythavutil-0.21_0
>libmythfreemheg-0.21_0 libmythlivemedia-0.21_0 libmythtv-0.21_0
>libmythui-0.21_0 libmythupnp-0.21_0 libogg libpng libraw1394
>libselinux-python libsemanage libsensors3 libsysfs libtiff libvorbis
>lirc-lib mesa-libGLU mythtv-backend policycoreutils qt
>0 upgraded, 60 newly installed, 0 removed and 0 not upgraded.
>Need to get 0B/23.4MB of archives.
>After unpacking 61.7MB of additional disk space will be used.
>
>Most of it are conventional FC6 components like X11, several libs
>etc.
>--
>Axel.Thimm at ATrpms.net


><< attach3 >>

_________________________________________________________________
Local listings, incredible imagery, and driving directions - all in one 
place! http://maps.live.com/?wip=69&FORM=MGAC01