On behalf of the TB as agreed in our meeting today (in Google Meet, not IRC as usual), use of /usr/local/ as a stopgap is approved for these specific uploads that are in the Resolute NEW queue at the moment, for CUDA specific packages only, into multiverse only, on one condition. We expect to move the path from /usr/local/ to regular distro FHS in the future[1]. We do not expect to be limited from doing so by the argument that users will be broken by the path move *because* we published it in the Ubuntu archive in /usr/local/. Mitigations need to be put in place for that now, such as appropriate release notes and documentation.
We did not discuss a specific timeframe for the expected move into regular FHS paths in terms of which future release post-Resolute we expect the move to happen. I think the expectation is "soon after Resolute", otherwise the TB may come knocking :-) [1] To be clear, once these arrive into Resolute, we expect the paths not to change in Resolute for the lifetime of the Resolute release. The future path change would happen in future Ubuntu releases only. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2141744 Title: [needs-packaging] cuda-13-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2141744/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
