Re: [mythtv-users] Re: Putting a toe in the CVS water
On Thu, 20 Jan 2005 09:21:13 +, Martin Ebourne [EMAIL PROTECTED] wrote: On Wed, 2005-01-19 at 23:39 +1100, Phill Edwards wrote: Oh - I thought these would be source RPMs as I got the list from http://atrpms.net/dist/fc2/myth-cvs/ I'm a bit confused now as I thought it a list of CVS RPMs would be source code. No, you can have pre-built binary RPMs of current CVS, just like you can of any release. There's nothing magical about CVS snapshots. In fact, I recommend you install those pre-built RPMs of CVS snapshots from Axel's repo before you try building your own. It'll help get you a feel for it. rpm-src http://apt.physik.fu-berlin.de/ fedora/3/en/x86_64 at-bleeding So the source RPMs don't come from Axel's repo? Ah, that is Axel's repo. ;) at-bleeding in fact. Sounds like you're using Axel's repo manually rather than via apt. In which case I'd get apt synaptic installed soon, makes life much easier. You'll find exactly the same source rpm's from axel's web site you included above - you just need to scroll the page to see the source rpms, which all end .src.rpm. Cheers, Martin. ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users Just a quick mail to say thanks for the info in this thread. I now have a mythtv box running the atrpms-bleeding cvs files. Next step, proper CVS builds ;) -- Regards, ~CM ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Re: Putting a toe in the CVS water
On Wed, 2005-01-19 at 23:39 +1100, Phill Edwards wrote: Oh - I thought these would be source RPMs as I got the list from http://atrpms.net/dist/fc2/myth-cvs/ I'm a bit confused now as I thought it a list of CVS RPMs would be source code. No, you can have pre-built binary RPMs of current CVS, just like you can of any release. There's nothing magical about CVS snapshots. In fact, I recommend you install those pre-built RPMs of CVS snapshots from Axel's repo before you try building your own. It'll help get you a feel for it. rpm-src http://apt.physik.fu-berlin.de/ fedora/3/en/x86_64 at-bleeding So the source RPMs don't come from Axel's repo? Ah, that is Axel's repo. ;) at-bleeding in fact. Sounds like you're using Axel's repo manually rather than via apt. In which case I'd get apt synaptic installed soon, makes life much easier. You'll find exactly the same source rpm's from axel's web site you included above - you just need to scroll the page to see the source rpms, which all end .src.rpm. Cheers, Martin. ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Re: Putting a toe in the CVS water
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. ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Re: Putting a toe in the CVS water
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.) Oh - I thought these would be source RPMs as I got the list from http://atrpms.net/dist/fc2/myth-cvs/ I'm a bit confused now as I thought it a list of CVS RPMs would be source code. 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 So the source RPMs don't come from Axel's repo? Regards, Phill ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Re: Putting a toe in the CVS water
Phill Edwards wrote: 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.) Oh - I thought these would be source RPMs as I got the list from http://atrpms.net/dist/fc2/myth-cvs/ I'm a bit confused now as I thought it a list of CVS RPMs would be source code. Those are pre-built binary packages of the source code from CVS from a particular date. I didn't see the rest of this thread, so maybe a daft question but if you want to use the CVS source code. ummm why don't you use CVS to get the source code? ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Re: Putting a toe in the CVS water
On Mon, 2005-01-17 at 23:59 +, Tom Hughes wrote: In message [EMAIL PROTECTED] Martin Ebourne [EMAIL PROTECTED] wrote: And I would strongly recommend them for any future CVS build. Get the src RPMs and drop a new checkout in rebuild (after you've sorted the macros out - see the atrpms list for a not-complete-set, sigh). Have you got a reference to that posting? Only I failed to find anything much when I looked despite finding innumerable requests for the information. http://lists.atrpms.net/pipermail/atrpms-devel/2004-November/000467.html That's the most complete list I've seen, thanks to Jarod. Still, misses perl macros and others. YMMV. Cheers, Martin. ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Re: Putting a toe in the CVS water
On Tue, 2005-01-18 at 12:08 +1100, Phill Edwards wrote: OK - thanks for the advice. Couple of questions: 1) How up to date with CVS are Axel's CVS RPMs? Check the package name. It's got the date in there of the checkout. 2) Is there any howto stuff amywhere on how to do it with Axel's CVS RPMs? Just as I thought I'd understood how to go CVS this adds a new angle to it so I want to make sure I've got my head around this before I start. Firstly, I don't know how experienced you are with RPM itself. Helps to learn a bit about the package system, you'll have a much easier time of system maintenance. This is the RPM book, and it's all on line: http://www.rpm.org/max-rpm/ Could do a lot worse than learning some of the basics. There's been some changes since it was published, most obviously that the building commands have been split out into a separate rpmbuild command. man rpm/rpmbuild will update you on that. My usual plan goes something like this (replace version as appropriate): (None of this involves being root.) 1. apt-get source mythtv 2. rpm -ivh mythtv-0.16.0.cvs20041220-87.src.rpm 3. cd ~/rpm/SPECS 4. vi mythtv-0.16.0.cvs20041220-87.rhfc3.at.spec (I add '.mje.1' to the Release: field so I know I built it) 4. rpmbuild -ba --without xvmcnvidia --without opengl_vsync mythtv-0.16.0.cvs20041220-87.rhfc3.at.spec (Choose the --with/--without options to suit your setup, see the mythtv-0.16.0.cvs20041220-87.rhfc3.at.spec file for the full list. Then, as root, install the binary package(s) it generates and lists at the end. You'll need a .rpmmacros file which contains something similar to this: %_topdir /home/martin/rpm In addition, you'll need to add the atrpms macros from this post to the same file: http://lists.atrpms.net/pipermail/atrpms-devel/2004-November/000467.html Having practised with rebuilding the version Axel provided you can then go in update the CVS to a newer version as you wish. Unfortunately Axel doesn't seem to include all the CVS directories so you can't just unpack the archive, cvs update, and then repack it. You should, however, be able to drop a new one in. So get a CVS checkout, tar.bz2 it up, and stick it in ~/rpm/SOURCES. Make sure the tarfile name matches what you put in Version: in the .spec file. If in doubt, unpack the one from the RPM (again, in SOURCES) and make sure yours looks the same. Again, vi the .spec file to update Version:/Release: as appropriate, then rebuild. I recommend you always at least bump the Release: when you rebuild so you don't end up with the confusion of differing packages with the same version number. Also best to add a quick note to the %changelog section for future reference. As to a HOWTO, the best person to write it is the one who's just done it all for the first time and has everything fresh. I'm bound to have forgotten a crucial step somewhere, for which I apologise in advance. ;) So presuming you manage to get somewhere with all this, how about writing it up in a howto adding it to Jarod's documentation, or the wiki? I understood wiping out all the mythtv rpms and then downloading, configuring, compiling and installing the CVS source code. How does using the CVS RPMs differ from this. Do they basically download and put the source code somewhere and from that point on it's the same as normal CVS? The main reason is that the end result is really no different from just installing a new version pre-built for you. This has lots of advantages - eg. easy, clean upgrades and downgrades (don't forget to backup the db). RPM will handle dependencies for you, so it may be possible to run precompiled myth modules against your CVS myth RPMs (depending on how far they've diverged - you can't run 0.16 and cvs together at the moment). But when they do diverge RPM will tell you. No need to try and remove your manual install before upgrading to a new pre-built version. Less breakage because all the files will be installed in the same places in the same way as they always were with the normal RPMs. And other good stuff too. Finally, though, building the RPMs is actually easier. It might seem counter-intuitive, but all of the instructions for configuring, building and installing myth are in the RPM .spec file, so they are always completely repeatable and you can't get them wrong. Your only job is to drop a new source tarball in as and when you want, edit a couple of lines of .spec file to match, and rpmbuild -ba xxx.spec. Hope this helps, Martin. ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Re: Putting a toe in the CVS water
Hope this helps, Thank you - that will help heaps. Could I also please confirm a couple of things: 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? 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 Regards, Phill ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Re: Putting a toe in the CVS water
On Mon, 2005-01-17 at 23:52 +0100, Axel Thimm wrote: do you know about ATrpms' CVs builds of MythTV? They are in the bleeding section, and may eat up your favourite shows and have your wife divorce you, but you can still treat them like usual packages (uninstall, downgrade etc). I would reocmmend it as a first step towards going full CVs self-build stuff. And I would strongly recommend them for any future CVS build. Get the src RPMs and drop a new checkout in rebuild (after you've sorted the macros out - see the atrpms list for a not-complete-set, sigh). Keeps the whole system much tidier and a lot easier to use; the dependencies and later upgrades are all taken care of for you by apt/rpm. Cheers, Martin. ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Re: Putting a toe in the CVS water
In message [EMAIL PROTECTED] Martin Ebourne [EMAIL PROTECTED] wrote: And I would strongly recommend them for any future CVS build. Get the src RPMs and drop a new checkout in rebuild (after you've sorted the macros out - see the atrpms list for a not-complete-set, sigh). Have you got a reference to that posting? Only I failed to find anything much when I looked despite finding innumerable requests for the information. Tom -- Tom Hughes ([EMAIL PROTECTED]) http://www.compton.nu/ ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Re: Putting a toe in the CVS water
On Mon, 2005-01-17 at 23:52 +0100, Axel Thimm wrote: do you know about ATrpms' CVs builds of MythTV? They are in the bleeding section, and may eat up your favourite shows and have your wife divorce you, but you can still treat them like usual packages (uninstall, downgrade etc). I would reocmmend it as a first step towards going full CVs self-build stuff. And I would strongly recommend them for any future CVS build. Get the src RPMs and drop a new checkout in rebuild (after you've sorted the macros out - see the atrpms list for a not-complete-set, sigh). Keeps the whole system much tidier and a lot easier to use; the dependencies and later upgrades are all taken care of for you by apt/rpm. OK - thanks for the advice. Couple of questions: 1) How up to date with CVS are Axel's CVS RPMs? 2) Is there any howto stuff amywhere on how to do it with Axel's CVS RPMs? Just as I thought I'd understood how to go CVS this adds a new angle to it so I want to make sure I've got my head around this before I start. I understood wiping out all the mythtv rpms and then downloading, configuring, compiling and installing the CVS source code. How does using the CVS RPMs differ from this. Do they basically download and put the source code somewhere and from that point on it's the same as normal CVS? ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
