[mythtv-users] Re: Putting a toe in the CVS water

[Martin Ebourne]

On Wed, 2005-01-19 at 12:35 +1100, Phill Edwards wrote:
> 1) With your technique, Martin, am I right in thinking that I don't
> explicitly _remove_ the existing packages? I download the ATRPM CVS
> packages, modify spec files, rebuild the packages and then install
> using rpm which _updates_ the packages that are already installed?

Spot on. The whole idea is that building your own packages and then
installing them is no different from someone else building them for you
(ie. Axel). There's no magic in making binary RPMs to use. ;)

> 2) Is the complete list of mythtv source packages from ATRPM  as follows:
> mythweather-0.16.0.cvs20050109-60.rhfc2.at.i386.rpm
> mythvideo-0.16.0.cvs20050109-60.rhfc2.at.i386.rpm
> mythphone-0.16.0.cvs20050109-4.rhfc2.at.i386.rpm
> mythnews-0.16.0.cvs20050109-33.rhfc2.at.i386.rpm
> mythmusic-0.16.0.cvs20050109-63.rhfc2.at.i386.rpm
> mythgame-0.16.0.cvs20050109-62.rhfc2.at.i386.rpm
> mythgallery-0.16.0.cvs20050109-63.rhfc2.at.i386.rpm
> mythdvd-0.16.0.cvs20050109-44.rhfc2.at.i386.rpm
> mythbrowser-0.16.0.cvs20050109-27.rhfc2.at.i386.rpm
> mythtvsetup-0.16.0.cvs20050109-88.rhfc2.at.i386.rpm
> mythtv-themes-0.16.0.cvs20050109-88.rhfc2.at.i386.rpm
> mythtv-frontend-0.16.0.cvs20050109-88.rhfc2.at.i386.rpm
> mythtv-backend-0.16.0.cvs20050109-88.rhfc2.at.i386.rpm
> mythtv-0.16.0.cvs20050109-88.rhfc2.at.i386.rpm
> libmyth-devel-0.16.0.cvs20050109-88.rhfc2.at.i386.rpm
> libmyth-0.16.0.cvs20050109-88.rhfc2.at.i386.rpm

Ah, there's a bit of assumption on my part. No, those are the binary
RPMs (the .i386 gives it away, that's the processor type). Source RPMs
have .src.rpm at the end and should be identical no matter what platform
it is for. (After all, it's still source at that point, so not platform
specific.)

Often multiple binary packages come from one source package. eg. mythtv-
frontend, mythtv-backend, mythtv, and libmyth* all come from the one
mythtv.xxx.src.rpm, and will be created automatically when you build
that.

If you've got rpm-src lines in your apt sources.list then you can
probably 'apt-get source <package>' to get the source RPM. Mine looks
like (for AMD64):

rpm-src http://apt.physik.fu-berlin.de/ fedora/3/en/x86_64 at-bleeding

If not, then go to the repository manually, and just download them using
a web browser. The address is as the line above, so would be:

http://apt.physik.fu-berlin.de/fedora/3/en/

Then follow it down into an architecture, then SRPMS.bleeding or
whatever.

Cheers,

Martin.