sarum9in
commented
6 years ago The first is probably a bug that was fixed in #57 (wrong ordering), the usual practice is to install the latest wrap. Currently you should always use the latest one, as meson install does.
Other enhancements are a good idea, but I don't see this happening without extensive design. We need to modify upstream.wrap file to specify all this. The general idea of wraps is that there should be no meson.build file, it should be provided by upstream instead. wrapdb should only host upstream.wrap. However since Meson is not very popular we support simple patch system that allows us to import other projects.
Just to make it clear, I don't think extensive information about wraps is going to be supported anytime soon, but I don't see it as impossible in the distant future.
Looking at zlib in wrapdb there are 9 non-consecutive revisions: 1, 2, 3, 2, 4, 6, 7, 8 over two versions 1.2.8 and 1.2.11.
It is not clear to me which version is the one I should use. It seems like that the older zlib version has more iterations on the wrap and therefore a more mature wrap. However I guess I would like to use as late version as possible of zlib.
I think you should have only one row per zlib version. It could also show some additional information like how "complete" is the wrap (does it build on all OSs, does cross building work, are the tests also ported? does it produce bit-by-bit identical output as the projects "native" build system?). You could show creation date of when this wrap was made or uploaded.