Roland Stigge wrote: >>Upstream puts just patches for in-tree compiliation in his tarball, we >>need them separately, for out-of-tree compiliation. > > What you are doing is taking upstream's code and adjusting it to > out-of-tree compilation. Since you are shipping patches (dpatch ...) > anyway, it still seems to be possible to prevent repackaging (which > should be tried as far as possible).
No. Atm you have to repackage it, or how do you want to 'unpack' the patch when some files (kconfig) coulnd't be patched in a way, that it is still non-interactive for autobuild? But I agree with you, that it should be discussed with upstream for the longer term, but that is your task as you have to connection to them. Until this is done, an modified tarball is the only solution. >>>Otherwise, we wouldn't even need a orig.tar.gz anymore. (?) >> >>Actually true, but imho there shouldn't be any native packages in Debian >>at all. > > This differs from common practice and standards within Debian. Feel free > to discuss it on [EMAIL PROTECTED] ;-) Sorry, no. Native packages are for packages that are specifically developed for debian. If we just need to rebuild a tarball, common use is to add +dfsg for the version when we need to rebuild it due to license issues. For other reasons, mostly a +debian tag is used. -- Address: Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist Email: [EMAIL PROTECTED] Internet: http://people.panthera-systems.net/~daniel-baumann/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
