Hi Michael, Am Freitag, den 15.06.2007, 20:29 +0200 schrieb Michael Schroeder:
On Fri, Jun 15, 2007 at 05:11:32PM +0200, Amilcar do Carmo Lucas wrote:
well, I still think this is a bug, debtransform should ignore all debian-*.tar.* files:
What's the point of having those tar files then?
There is no point, more then one debian dir is useless. But I think I know why Amilcar put them there. Backporting applications to different debian/ubuntu releases. But this is done in using correct values in debian/control for build and/or install dependencies. Example: wine in ubuntu feisty and new dev release gutsy. It will use two different versions of libstdc++, to make it easier for the ubuntu backporting guys, you use the following notation: libstdc++4.2-dev | libstdc++4.1-dev | libstdc++-dev in the Build-Dependency section. The build environment of debian/ubuntu (e.g. the sbuild or pbuilder) is reading those dependencies correctly. It reads from left to right: if libstdc++4.2-dev is availbale, use it first if libstdc++4.2-dev is not there, check for libstdc++4.1 and use it when it's available if the first two are not available use the last version. there is no need for different debian.tar.gzs or better to say different debian/ directories.
package contains more than one tar file: kdevelop-3.4.1.tar.bz2 debian-xUbuntu_6.06.tar.gz dpkg-source: error: cannot open .dsc file /usr/src/packages/SOURCES.DEB/*.dsc: No such file or directory
I have added support for some configuration options to debtransform. You can now override the default matches with some .dsc file attributes:
Debtransform-Tar: <pristine-tar-ball> Debtransform-Series: <quilt-series-file> Debtransform-Files-Tar: <tar-ball-containing-debian directory files>
How do you use them with dpkg-source? I don't think this is a good idea to go far away from the default debian standard. Regards, \sh -- Stephan Hermann eMail: sh@sourcecode.de Blog: http://linux.blogweb.de/ JID: sh@linux-server.org OSS-Developer and Admin