We agreed during the MIR meeting that a generic tooling as part of
debhelper would be the best way, didn’t we?

See my arguments above different upstream policies in different source
packages, where if we start introducing this in a per-package base, that
would create divergences between projects. Does it make sense to have
this centrally managed (by our Rust toolchain expert, ideally?).

That way, we can go beyond trimming the windows crates, like tree
shaking and so on?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2048781

Title:
  [MIR] authd

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/authd/+bug/2048781/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to