> Compare these oddities with the fact that there are _no_ problems for you > to package your program non-native while including a complete debian/ > subdir in the upstream version and I hope you understand why it's better > to package your program non-native.
So this is where I get lost: how can you package as non-native *while including a complete debian/ subdir in the upstream version*? It looks to me that as soon as the upstream includes debian/ it looks native to tools and then you get full-source upload, no diff, and all the problems people have mentioned (which are real, but I am in that nice position where I have CVS write upstream, being one of the authors, and I don't mind upstream being a bit late/unsync'ed). If that can be done, I'm all for it. One of my primary reasons for having the debian/ dir upstream is so as not to lose it :-) YA
