@spad@ikke @alpinelinux `apk search yq` or `apk add -s yq`.
You’re right that pkgs.a.o is not very helpful for this.
BTW, the goal is to make ppl stop using the old package name.
@jakub@ikke I know the intent in this case but it applies to anything with a metapackage. The case I was envisioning was I find a dockerfile using 3.20 and installing the package yq. I don't know what that package does so I search on pkgs and get zero results. I do apk search yq and get some results but none of them are "yq", they're "yq-go", "yq-python" etc. So apart from actually installing it myself to see what it is, there's no simple way to find out.
@spad@jakub These are not meta packages in that sense (there is no explicit package with that name in the index).
There is nothing indexing or exposing these virtual provides at the moment, except by looking at what each package provides (apk info --provides <package>).
Gregory's Server
@jakub @ikke I know the intent in this case but it applies to anything with a metapackage. The case I was envisioning was I find a dockerfile using 3.20 and installing the package yq. I don't know what that package does so I search on pkgs and get zero results. I do apk search yq and get some results but none of them are "yq", they're "yq-go", "yq-python" etc. So apart from actually installing it myself to see what it is, there's no simple way to find out.