severity 619131 wishlist thanks On Mon, 2011-03-21 at 15:44:53 +0100, Joerg Jaspert wrote: > we want a new field to be put into .dsc files please. This should be a > list of all "override" entries for this package. That is, a list > consisting of every single binary and one line for the source package > itself.
Just a nomenclature note here, overrides is what the archive (whatever implementation that might be, dak, dpkg-scanpackages, etc) applies to the fields from the binary/source packages, which is the original source of the information. > And the background for this stunt: This way we can process NEW adding > overrides for every package, not requiring a new NEW run for every > single arch of packages that build different names on different > architectures. While we COULD do it by extracting the source, looking at > the debian/control and parsing that, this gets increasingly hard with > different source formats, possible source tarballs being elsewhere > (think of -2 uploads and source in pool) and other processing > trouble. Compared to the relative ease dpkg-* can do it at build time it > seems better to do it there. (also, this way others profit too) Neither of these are truly possible w/o breaking current assumptions. There's no guarantee at all that the binary stanzas in debian/control correspond with what will be shipped in the .changes file. The only stanza that is guaranteed to be constant is the source one. In addition it's currently supported to ship less packages than the ones listed in debian/control, even if dpkg-genchanges will warn about it. And besides changing or adding new binary stanzas to debian/control, adding new files not present in debian/control has been supported for a long time via dpkg-distaddfile. (I've just fixed an unused variable usage in dpkg-genchanges due to files added by dpkg-distaddfile in some conditions, which I'll include in my next push.) Anyway, recording entries on the archive for things that might never appear seems a bit crufty, but you are the ones handling dak. Also I'm not sure how you are currently handling the NEW processing regarding the overrides, but from what I've seen I've got the impression package sections and priorities are not usually overriden on that stage (as they used to be)? If that's the case then the archive software could as well initialize the overrides automatically with the entries from the binary packages in the .changes file. regards, guillem -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
