-
Notifications
You must be signed in to change notification settings - Fork 582
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cmd: Correctly name the "Ubuntu" and "Arch" NVIDIA methods #3978
Conversation
Applying distribution names to widely used methods is a little disingenuous, so let's say what they really arch. The "Ubuntu" method is in reality a management method employed only on multiarch Linux distributions, used on Ubuntu and portable to Debian. The "Arch Linux" method is in fact just how classic "bi-arch" Linux distributions work, i.e. multilib systems with lib32/lib64. Signed-off-by: Ikey Doherty <[email protected]>
Fair disclaimer: This one is a bit opinionated. |
Codecov Report
@@ Coverage Diff @@
## master #3978 +/- ##
==========================================
+ Coverage 75.97% 75.98% +<.01%
==========================================
Files 423 423
Lines 36505 36505
==========================================
+ Hits 27734 27737 +3
+ Misses 6833 6830 -3
Partials 1938 1938
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would suggest renaming them to debian-multiarch
and multilib
, as there are other schemes of multiarch (such as the scheme used by Exherbo).
As an aside, I don't think this code is actually working like it should, as I don't see where it would match code installed in multilib/biarch directory paths. For example, Fedora and openSUSE install the libraries to |
I like this rename, thanks for doing this! I would really like to keep the old configure options around for compatibility for a little bit in configure just so that downstream packagers (we might not know) don't get their packaging broken (showing a deprecation warning). But maybe this is not really needed given that we know most of our packagers. |
@mvo5 I think when it comes to build-side configure flags, I don't think deprecation warnings are necessary beyond just throwing an error (and kill the build) when the old option is used. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, feel free to iterate on the name (agree upon something locally at the rally please)
We could have a nasty compatibility set of options .. :) |
@ikeydoherty trivial conflict in one file after merging other nvidia PR |
ok |
Applying distribution names to widely used methods is a little disingenuous,
so let's say what they really arch. The "Ubuntu" method is in reality a
management method employed only on multiarch Linux distributions, used on
Ubuntu and portable to Debian.
The "Arch Linux" method is in fact just how classic "bi-arch" Linux
distributions work, i.e. multilib systems with lib32/lib64.
Signed-off-by: Ikey Doherty [email protected]