Due to rather minimalistic wiki/docs for Alpine Package Keeper, I have failed to determine why it appears to refuse repository tags when specifying packages part of a virtual dependency.
The question is, is this by design, and if so, what is the motivation behind this difference?
Minimal reproducible example:
docker run --rm -it alpine:3.18
echo @v316 https://dl-cdn.alpinelinux.org/alpine/v3.16/community >> /etc/apk/repositories
apk add --no-cache --virtual .example librdkafka-dev@v316
This produces an unexpected error:
ERROR: 'librdkafka-dev@v316' is not a valid child dependency, format is name([<>~=]version)
No error with:
apk add --no-cache librdkafka-dev@v316