In the loop, why is it a read-only variable? about dkms HOT 4 OPEN

There is already a PR for this: #415

from dkms.

The file name also needs to be optimized. If there are multiple -k or --all, it becomes too long, for example: i40e-2.25.9-kernel4.18.0-425.3.1.el8.x86_64-x86_64-kernel4.18.0-425.19.2.el8_7.x86_64-x86_64.dkms.tar

from dkms.

@wubo0067 as mentioned in the PR, do you mind adding a test so we don't re-introduce this in the future?

I'm not sure what you mean by "The file name also needs to be optimized" - if you can submit a PR that would be appreciated.

from dkms.

@evelikov
1: Honestly, I'm not sure what kind of tests meet your requirements. If you have examples, I can give it a try.
2: Filename optimization refers to the situation where, under -k or -all, if there are multiple kernel patch versions in the system, the generated xxx.dkms.tar filename will be very long. I want to think about how to optimize it and try to make a PR.

from dkms.