Discussing with @kit-ty-kate on #6253, we figured out some remaining things to be done in the automatic upgrade mechanism to sanitise it.
Opamfile 1.2 was split in 3 files : opam, descr and url. Opamfile 2.0 merged all these files in the opam file itself. There is an automatic format upgrade mechanism that permit to handle 1.2 opamfiles. But, currently, descr and url files are still read even for opamfile 2.0. We suppose that it was done during transitional phase between 1.2 -> 2.0, but it was 8 years ago, we can remove it safely today.
There is a first step to sanitise the automatic upgrade : contain descr & url file reading in the format upgrade code. It'll permit to be consistent, and no longer require from api users to handle that case.
Plus, having a well contained format upgrade in the codebase will help us to further opamfile format upgrades.
Discussing with @kit-ty-kate on #6253, we figured out some remaining things to be done in the automatic upgrade mechanism to sanitise it.
Opamfile 1.2 was split in 3 files : opam, descr and url. Opamfile 2.0 merged all these files in the opam file itself. There is an automatic format upgrade mechanism that permit to handle 1.2 opamfiles. But, currently, descr and url files are still read even for opamfile 2.0. We suppose that it was done during transitional phase between 1.2 -> 2.0, but it was 8 years ago, we can remove it safely today.
There is a first step to sanitise the automatic upgrade : contain descr & url file reading in the format upgrade code. It'll permit to be consistent, and no longer require from api users to handle that case.
Plus, having a well contained format upgrade in the codebase will help us to further opamfile format upgrades.