[vdr] compiling the xine-1.2 with external ffmpeg
Hi list Does anyone use checkinstall instead of make install in order to build a xine-lib debian package? I know how use it along with ffmpeg, but I'm not sure how to use it along with xine-lib 1.2 since this one provides more than just one package - I guess there are at least three: libxine1, libxine1-bin, libxine1-dbg but I'm not sure that is all of it. Point is: if you build xine-lib-1.2 on your own you can't have conflicting distro packages like libxine1, libxine1-bin, libxine1-dbg and so on installed. Now many programs will complain about that, since they only check the presence of a distro package and NOT the effective presence of any files those packages provide. The only way I know to get around this is start building those programs on your own as well, but editing the control file first. So you can remove xine-lib dependencies and then build this program successfully. I somehow hate the thought of it - it's not the way how this has to be done and might cause problems sooner or later. So anyone knows how to make the perfect debian package out of this xine-lib 1.2, so it provides every debian distro package? OS I use is Intrepid Thanks in advance. _ Werden Sie Mitglied der neuen Windows Live Messenger Familie! http://download.live.com___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] compiling the xine-1.2 with external ffmpeg
Does anyone use checkinstall instead of make install in order to build a xine-lib debian package? This is not the right way to build a debian package, it is a dirty hack. All the files that are necessary for building a debian package are already there if you check xine-lib-1.2 out using 'hg clone http://hg.debian.org/hg/xine-lib/xine-lib-1.2'. With 'debuild -uc -us -rfakeroot' in the xine-lib-1.2 directory, the xline-lib gets compiled and you have debian packages afterwords one directory up. At least this is the way I build my ubuntu packages for xine-lib with vdpau patches. Gerald ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] VDR developer version 1.7.3
On 06.01.2009 16:06, Klaus Schmidinger wrote: - Recording files larger than 4GB or with more than 255 separate files hasn't been tested yet. + The index file format has been changed to support file sizes of up to 1TB (previously 2GB), and up to 65535 separate files per recording (previously 255). Untested indeed. Theres still this line in recording.h: #define MAXVIDEOFILESIZE 2000 // MB Just in case it slipped through. Cheers, Udo ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] VDR developer version 1.7.3
On 24.01.2009 15:19, Udo Richter wrote: On 06.01.2009 16:06, Klaus Schmidinger wrote: - Recording files larger than 4GB or with more than 255 separate files hasn't been tested yet. + The index file format has been changed to support file sizes of up to 1TB (previously 2GB), and up to 65535 separate files per recording (previously 255). Untested indeed. Theres still this line in recording.h: #define MAXVIDEOFILESIZE 2000 // MB Just in case it slipped through. Thanks. I forgot to make this two, one for PES and one for TS. Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] compiling the xine-1.2 with external ffmpeg
I demand that Gerald Dachs may or may not have written... Does anyone use checkinstall instead of make install in order to build a xine-lib debian package? This is not the right way to build a debian package, it is a dirty hack. All the files that are necessary for building a debian package are already there if you check xine-lib-1.2 out using 'hg clone http://hg.debian.org/hg/xine-lib/xine-lib-1.2'. Or if you grab a snapshot tarball (but not from Debian experimental, since that tarball was built using make dist; OTOH, you have the .diff.gz). With 'debuild -uc -us -rfakeroot' in the xine-lib-1.2 directory, the xline-lib gets compiled and you have debian packages afterwords one directory up. As well as source packages, which you (probably) don't need or want. I normally just use debuild binary, but adding in the signing-prevention options is useful for others. It does depend on whether you're distributing or not, but if you are, I suggest make dist-gzip, unpack the tarball, copy the Debian directory into it, add a changelog entry (it's worth mentioning the changeset ID) then build. At least this is the way I build my ubuntu packages for xine-lib with vdpau patches. You have the right idea. :-) -- | Darren Salt| linux or ds at | nr. Ashington, | Toon | RISC OS, Linux | youmustbejoking,demon,co,uk | Northumberland | Army | + Output less CO2 = avoid boiling weather. TIME IS RUNNING OUT *FAST*. A stitch in time saves nine. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] compiling the xine-1.2 with external ffmpeg
oh, the maintainer of the package himself replies to me :) Thanks for the corrections Darren. Gerald ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] VDR developer version 1.7.3
Klaus Schmidinger a écrit : On 24.01.2009 15:19, Udo Richter wrote: On 06.01.2009 16:06, Klaus Schmidinger wrote: - Recording files larger than 4GB or with more than 255 separate files hasn't been tested yet. + The index file format has been changed to support file sizes of up to 1TB (previously 2GB), and up to 65535 separate files per recording (previously 255). Untested indeed. Theres still this line in recording.h: #define MAXVIDEOFILESIZE 2000 // MB Just in case it slipped through. Thanks. I forgot to make this two, one for PES and one for TS. Hi Klaus, Why this 1TB limitation ? Guy ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] VDR developer version 1.7.3
On 24.01.2009 23:23, Guy Roussin wrote: ... Why this 1TB limitation ? The index file uses 8 byte per entry, two of which are now used for the file number, one bit is used to identify independent frames, and 40 bits are used for the actual file offset. The remaining 7 bits are reserved for future use ;-) 40 bit allows access to 1TB, which, assuming 2GB per hour (for current SD recordings) means a single file recording can be some 500 hours long. That makes 20 whole days in a single recording. Ok, let's assume HD recordings need like 4GB per hour, then you still have 10 days in a single recording. If you actually have a need to record more than that in one single recording, we can use some of the reserved bits to increase that number ;-) Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
