-
Notifications
You must be signed in to change notification settings - Fork 164
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
When there's only one version of a module, allow to omit the module version. #18
Comments
For someone want to use dkms install frequently ,I suggest you write your own script to do this . |
I need this because I modify module source directly in |
In most situation ,Linux user have some dkms modules installed ,I do not think that we need to change function codes for this debuging or convenience purpose . |
I don't think I fully understand what your concern is, but at least this kind of change won't break existing functionality. The old behaviour (version explicitly specified) will keep working. |
@khfeng |
I don't think you really understand what I am asking for. To simply put: why do we need to specify version number, when there's only one version available? |
If I'm understanding right, this is entirely different from, say, #5. I think the following should be acceptable:
Because this is a behavioral change, I think we should only enable this with a flag ("-1" perhaps?). That is, I think it's okay to do this as an optional change. I don't want this to devolve into a semantic change in existing functionality like #5 would be, as a semantic change could result in unintended consequences for distributions depending on DKMS. |
@khfeng |
As someone who regularly remove/install dkms, I found specifying the module version is redundant in most cases.
I'd like to use
dkms install <module>
instead ofdkms install <module>/<version>
, if there's only one version of the module.If this new behavior is acceptable and does not break scripts that already depend on DKMS, I can make a patch for this.
The text was updated successfully, but these errors were encountered: