I don't know if this changes are that important, but vdr-1.4.7 is out since 12.05.2007. VDR 1.4.7 * Fixed a busy loop in fast forward if the next video data file is missing (thanks to Reinhard Nissl). * Fixed handling frequencies in NitFilter::Process() (thanks to Anssi Hannula). * Fixed handling ChannelUp/Down keys if there is currently a replay running (thanks to Marco Schlüßler). * Increased the maximum number of CA system ids to cope with the AlphaCrypt CAM's version 3.11 firmware.
We already know about this version. We have a vdr-1.4.7 ebuild in the vdr-testing overlay. And also we have a vdr-1.5.5 ebuild in a dedicated vdr-1.5 overlay. Both are available via layman. For the 1.4.7 ebuild we just are not sure if it is already good enough for the official tree. It now uses the vdr extensions-patch instead of a special gentoo patchset. But that offers a lot of switches around 20-30. And the ebuild contains a lot of code perhaps better moved somewhere else.
(In reply to comment #1) > We already know about this version. > > We have a vdr-1.4.7 ebuild in the vdr-testing overlay. > And also we have a vdr-1.5.5 ebuild in a dedicated vdr-1.5 overlay. > Both are available via layman. > > For the 1.4.7 ebuild we just are not sure if it is already good enough for the > official tree. It now uses the vdr extensions-patch instead of a special gentoo > patchset. But that offers a lot of switches around 20-30. And the ebuild > contains a lot of code perhaps better moved somewhere else. > Sorry for the noise, i didn`t know about the vdr overlay. I will take a look at it!
(In reply to comment #1) > For the 1.4.7 ebuild we just are not sure if it is already good enough for the > official tree. It now uses the vdr extensions-patch instead of a special gentoo > patchset. But that offers a lot of switches around 20-30. And the ebuild > contains a lot of code perhaps better moved somewhere else. Why not putting it into ~testing so more people (not using an overlay for every single app) could actually test it and report any bugs/problems directly to the bugtracker? :) I always thought that's the purpose of ~testing.
(In reply to comment #3) > > Why not putting it into ~testing so more people (not using an overlay for every > single app) could actually test it and report any bugs/problems directly to the > bugtracker? :) I always thought that's the purpose of ~testing. > As zzam already mentioned, this is maybe just a simple version bump for the vdr itself, but not for the ebuild, as it seems there are many changes. So if the developers decide that it is not ready for the tree we should accept this. By the way what is wrong with using layman: emerge layman echo "source /usr/portage/local/layman/make.conf" >> /etc/make.conf layman -a vdr-testing (or vdr-1.5,vdr-experimental for the brave) Then unmask vdr in package.keywords and you are done.
added vdr-1.4.7-r4 to main portage tree, new patchset with new use-flags ! check Description for every use-flag ! HF :)
