Hi, Guillem Jover wrote:
What you describe is a binNMU but with a different suffix. Maybe we could come up with a generic syntax for binNMU-style versions, which could include backports and the like.
That would be difficult. For example, for my cross-toolchain backports I use "~debian4.0+b1" as a suffix, with "debian" being replaced by "ubuntu" for Ubuntu builds etc.
In principle the only way to be sure would be to add another special character ("#" springs to mind), but that would be a pretty invasive thing.
Although I'm not sure this is worth it, in most cases, you'll need to modify the source anyway, and in the others having an additional diff.gz is not that much (that does not take into account native packages, but there should not be that many of those anyway).
Well, all current toolchain packages auto-backport without any source changes; I'd expect a lot of packages already work fine.
[patch adding DEB_SOURCE_VERSION]
I don't think this is a good idea, it makes automatically building those packages rather cumbersome, and difficult to reproduce.
For normal binNMUs, nothing changes, as the current behaviour is still the default. When (automatically) building a backport with a nonstandard version number, all that has to be done is save the version number before the addition of the extra changelog entry, and pass that as the contents of DEB_SOURCE_VERSION during the build process.
Omitting this step leaves us at the status quo, so there is no regression in the patch either.
Also the patch is wrong, Source-Version != source:Version, otherwise we'd not have introduced the new variables.
Well, at this specific point, they are initialized to the same value, so I'd expect them to be much the same at least at this point in time.
Simon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
