@alpinelinux re: yq change, unless I'm missing something...

@alpinelinux re: yq change, unless I'm missing something aliases/metapackages don't show up in the pkgs search site or using "apk search", you have to go look at the APKBUILD file of the thing it's an alias to, which kind of defeats the point.

Is there actually a way to tell that a "yq" package exists and what it actually links to, other than already knowing it?

Like 22 May at 13:48 | Wall-to-wall | Open on mastodon.linuxserver.io

5 comments

Kevin

@spad @alpinelinux apk search cmd:yq is the best way to find what packages provide specific tools.

22 May at 14:13 | Open on ipv6.social

Adam :lsio:

@ikke @alpinelinux that's useful, but still doesn't tell me that a metapackage called "yq" exists or what it installs.

22 May at 14:17 | Open on mastodon.linuxserver.io

Jakub Jirutka 🇪🇺🇺🇦

@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.

23 May at 0:49 | Open on social.jirutka.cz

Adam :lsio:

@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.

23 May at 6:37 | Open on mastodon.linuxserver.io

Kevin

@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>).

23 May at 7:16 | Open on ipv6.social