Open timpatt opened 3 months ago
timpatt
commented
3 months ago Ok - I've since found out that you can click on the tags under the "Available Packages" heading on the LHS of the page, but not on the (identically looking) tags that exist on each binary package. Some tweaking here might still be good.
memsharded
commented
3 months ago Hi @timpatt
As an additional approach, you might consider using the conan list tools and conan graph explain.
They have --filter-profile, --filter-settings, etc, that can be used to filter based on settings. They can generate json output that you can further analyze automatically. The conan graph explain does a smart diff between the existing packages and what you need. This allows to do even more powerful and advanced searches for binaries.
In any case not that for many production usages, the approach for ConanCenter packages is actually to build them and store your own binaries in your own private server, please have a look to https://docs.conan.io/2/devops/using_conancenter.html and https://docs.conan.io/2/devops/conancenter/hosting_binaries.html
There are often a whole heap of binary packages available for any given conan package. Unfortunately, the current layout makes it very difficult to actually get a good idea of what binary packages are available at a glance. Usually, I'm interested in understanding if a package is available for my particular use-case before then diving into the details of the options, dependencies, etc.
Perhaps an expandable table summarising the top-level "tags" (eg. "Windows", "shared", "x86_64", "Release", etc) would be better a better initial representation of this data? The user could then expand any particular version to explore its details.
Alternatively, the current layout might work if we were able to trivially filter based on "tag", with the option of also using an "advanced" filter that would allow filtering on all other fields.