MEPIS Community Forum

There's a git branch that has that enabled (PVR=watch and record TV), plus a PPA with packages and source. It supports a variety of backends for the PVR functionality, including mythtv, but the Ubuntu packagers suggest tvheadend (which would also need packaging)

I am not exactly sure what a M11 CR pkg is, but if it is a .deb and not to much trouble I would be interested. I have started using XBMC recently with an p4 I had laying around, I really have grown to liking it. The plan was to add a pvr function to it this weekend so I did some googling and came accross this thread.

Mepis 11 is based on Debian Squeeze. The M11 Community Repository is where you can find newer/updated packages than the ones provided by the Squeeze repos, or even packages that don't exist there.

You can add the Mepis Community Repositories (Main and Test) to your /etc/apt/sources.list:

#deb http://main.mepis-deb.org/mepiscr/repo/ mepis11cr main non-free
#deb http://main.mepis-deb.org/mepiscr/testrepo/ mepis11cr test

Be advised that new, untested packages usually go in the Test repo first.

I can't remember anything from the test CR ever causing a problem. Plus sometimes feedback from Users who try something in test can be slow.
But it is testing that will catch the occasional problem that might pop up.

Thank you, but you sure have a short memory. The original set of KDE 4.6.5 packages in testing caused a bit of a kerfuffle.

Installing a single package from the testing CR is usually fine.
Doing your regular updates with testing enabled can occasionally cause problems.

Just enable testing long enough to install the program you're interested in and pay attention to what else Synaptic wants to do in the process - especially if you see it's going to remove some packages. One accidentally screwed up dependency caused Synaptic to want to remove most of KDE. We do fix those issues pretty quickly once we've discovered them, but they're why we have testing repos.

That said, 95%+ of testing packages don't have any issues.

I did remember that kerfuffle, but that sort of thing is such a rare occurrence that I didn't see any reason to bring it up. Our repo maintainers are the best.

I thought that problem was more of a 'bridge too far' kind of thing. Rather than a real mistaken build.
At any rate it's always been recommended to use them for a specific program and then disable them in normal usage.

Is there any particular reason why that approach is recommended rather than leave the sources.list alone and use 'apt pinning'? I mean, you could, I assume, just as easily 'pin' the testing repo to not allow updates but to allow individual packages with the '-t' parameter in apt.

I'm only asking because I am more use to this approach in other Debian based systems I have run.

cheers,
Greywolf.

Edit:

Sorry, I did not mean to drift OT &/or hijack the thread!
I would be interested in such a PVR package for sure.