So, that was my idea for the algorithm:
1. We add the ability to generate a substvar-like output to the vendor script,
e.g. --substvar. It goes to stdout, and defines 'dh-cargo:Vendored-Sources'
2. In the clean target in dh-cargo, we generate d/dh-cargo-source.substvars in
d/rules.
3. In the configure target, where we previously did the sanity check, now the
check is:
If no field:
error("add substvar support")
If hardcoded field (== no mention of dh-cargo-source.substvars in
d/source/options):
warning("add substvar support")
If field mismatch:
previous error
HOWEVER that doesn't work for one really stupid reason: there is no long
option equivalent to -Tdh-cargo-source.substvars. And
debian/source/options only works for long options.
That would be the reason I didn't do it like this in the first place, I
guess.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2115573
Title:
Have dh-cargo-vendored-sources update debian/control rather than just
verify it
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dh-cargo/+bug/2115573/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
