>> There is already a publicly available VDR repository offering the >> current stable & developer versions, along with all previous versions: >> http://www.tvdr.de/download.htm > > ?? these are tarballs, where is the version control system? That would be a question for Klaus, the author of VDR. I will say that whatever system he uses for `version control` has seemed to work fine in the 12 years or so I've been using VDR. If it's that important to you to download from git instead, you can use the following mirror: https://projects.vdr-developer.org/git/vdr.git/ Don't expect that to be of any real advantage however. VDR is not developed that way. >> It's best to refer to VDRs packaged documention. You can get the >> channels.conf format definition with `man 5 vdr`. > > Good point, but I have only 2.2 installed, so where get I the backward > informations .. should I extract all theses tarballs and read through > them .. you see my point? That's not necessary. Klaus has designed VDR in such a way that things don't break when they're updated. You only need to refer to the documentation of the most recent version. >> That wiki shouldn't be viewed as a main reference point in general but >> especially for scanning. > > And the main ref is https://www.linuxtv.org ... which is not updated? That page is certainly outdated and has never been considered a main reference. People by far have always used vdrportal, another forum which is now defunct (which focused on NA/SA), and the VDR mailing list as their main reference points. > What I said, nobody use the vdr format of dvbv5-tools, since it > is broken and now, Chris and I want to fix it. That, and there are other tools that are easier and/or simply work better for some people (such as nscan). >> I'd recommend posting to the VDR mailing list where you'll find more >> people who use and would be affected by these changes. Additionally, >> you could inquire at vdr-portal.de, which is one of the most supported >> VDR forums for both users and developers. > > Chris and I want to patch something in v4l-utils which is broken > and YOU make the assumption that our patches are not OK ... and now, # > I have to ask someone other on a different projects ML and their portal? I made no claim whether your patches are ok or not. I simply said you should not intentionally or unnecessarily break backwards compatibility, and I based that comment on what others have said. Additionally, if you want to update tools to be more usable why wouldn't you want input from the very people you hope will use them?! Suggesting you should inquire on the VDR mailing list is clearly NOT bad advice. > If you have a doubt about the patches from Chris and mine, make a test and > if you see any regression it would be great to post your experience here ... Since everything I say is met with resistance, I think I'll pass. I only replied in this thread to help but now I've lost interest. Good luck with your patch however. -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
