I use this file (http://download.nvidia.com/XFree86/Linux-x86_64/latest.txt) to trigger driver updates. Currently it points to 390.129 which is the latest driver of the legacy branch (390.xx). Before it pointed to the latest driver of the Long Lived Branch and this would be the one I’m actually interested in.
Can you maybe have several “latest.txt” files, each pointing to the latest driver of its particular driver branch?
The content of latest.txt changes frequently. Usually it tracks the newest drivers of the Long Lived Branch. So it is still updated in some form. But the last update went backwards to the latest update of the legacy branch.
I guess that updating latest.txt is part of some publishing script, but it was designed before several maintained legacy branches were kept around in parallel. Now, with these legacy branches which also receive updates from time to time they collide by writing all into the same file and you get a last-writer-wins situation.
Therefore I mentioned the idea to use:
latest-long-lived-branch.txt
latest-official.txt
latest-legacy-390.txt
etc.
… or something similar.
For me it it’s important to have some way that an automatic script can determine the latest driver version for automatic installation.