This PR is a proposed fix for #19. This allows one to set the customization.cfg variable $_driver_version to latest, and this will select the latest driver. My use case for this is that I follow the Git log whenever there are new changes, but it's hard to tell which versions are the ones that I want, and it would overall be easier to set-and-forget "latest" :frog:
This implementation leverages the fact that the list of drivers in the package selector is in order. For the latest regular driver, we just take the first one. For the latest Vulkan beta driver, we take the only one.
A possible consideration: for the regular branch, I see that there is both a Latest Production Branch Version and a Latest New Feature Branch Version. This PR does not differentiate between the two, e.g. with a latest-production and latest-feature branch. I am open to implementing this, I just haven't done so because this would put the onus on the maintainer (@Tk-Glitch) to maintain this feature going forward, as opposed to the current state in which just taking the very first driver is unlikely to need any future corrections.
This PR is a proposed fix for #19. This allows one to set the
customization.cfg
variable$_driver_version
tolatest
, and this will select the latest driver. My use case for this is that I follow the Git log whenever there are new changes, but it's hard to tell which versions are the ones that I want, and it would overall be easier to set-and-forget "latest" :frog:This implementation leverages the fact that the list of drivers in the package selector is in order. For the latest regular driver, we just take the first one. For the latest Vulkan beta driver, we take the only one.
A possible consideration: for the regular branch, I see that there is both a Latest Production Branch Version and a Latest New Feature Branch Version. This PR does not differentiate between the two, e.g. with a
latest-production
andlatest-feature
branch. I am open to implementing this, I just haven't done so because this would put the onus on the maintainer (@Tk-Glitch) to maintain this feature going forward, as opposed to the current state in which just taking the very first driver is unlikely to need any future corrections.