Hi,
On 7/11/24 9:55 PM, Jonas Smedegaard wrote:
Quoting Philipp Kern (2024-07-11 21:13:42)
I'd - at the very least - would like to see a statement why a fork is
necessary. Innovation can happen in forks. But they don't necessarily
need to be in the archive to make a point.
dh-cargo is designed to repackage prepackaged code projects already
distributed through crates.io. If you do an NMU where you include the
preferred form for distribution, you are kindly asked to stop doing
NMUs because that messes with how the Rust team deliberately avoids
tracking the actual source for the code projects distributed.
I listed in the ITP a list of features lacking in dh-cargo, which I need
for packaging Rust-based code projects in Debian from preferred form for
distribution source. I do not need all of the features for all of them,
but some of them sometimes.
This still does not answer the question why a fork is the better option
instead of working with the people behind dh-cargo to integrate those
features into the codebase?
cheers,
Birger
