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
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
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. :-)
oh, the maintainer of the package himself replies to me :) Thanks for the corrections Darren.
Gerald
-
Darren Salt -
Gerald Dachs -
Stefan Ellenberger