Received: from mailout02.platinum-mail.de (mailout02.platinum-mail.de [IPv6:2a0a:4cc0:0:fc1:b5ed:8d94:185a:b8db]) by gbr-app-1.alpinelinux.org (Postfix) with ESMTPS id 93A3F223603 for <~alpine/users@lists.alpinelinux.org>; Fri, 20 Feb 2026 12:16:52 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mailout02.platinum-mail.de (Mail Service) with ESMTPS id 747AF9A28F3 for <~alpine/users@lists.alpinelinux.org>; Fri, 20 Feb 2026 12:16:49 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; d=achill.org; s=mail; c=relaxed/simple; t=1771589809; h=date:message-id:subject:from:to; bh=M35SuYN2DE8bh4op3iEpCXRxBJjQ39mZud0U9lBg/Zg=; b=gWVZZ8it4W0r4pVrpxiMgSudvHpIptLcUHLBgsvnNnC4l5ltFNnqIr+njREyaHT3/GRWTJ+/JfL OBDPOoUfxwEg4JF7k41drDVEEvC++wUeYOkN8S5a42NRSmWcWfuiftyDa7kYxOoS5lVOG72XDvk5f vJWAXGsBUy01/EN2dFvsucXgpjxid/JXYG9fj1iH/CBvWISRzRUo+DvFpNhY+X5c0VXv5XdTUX09p bb9j/7u43alo/NEtguJBAxzOm0xZkxxGVshZf/J+Axx+R5K2ryVqxvsyuqRaPpeI1VL9sZRY3qH+u 9mlqj/aTODcnulJmN9w6RSLyCSXbfyRpKTjA== Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Date: Fri, 20 Feb 2026 13:16:48 +0100 Message-Id: Subject: Re: Using repository tags ("@tag") with virtual packages From: "Achill Gilgenast" To: =?utf-8?q?Andreas_K=C3=A4h=C3=A4ri?= , <~alpine/users@lists.alpinelinux.org> X-Greeting: Hi mom! Look, I'm in somebodys mail client! X-Mailer: aerc 0.21.0 References: In-Reply-To: Content-Type: text/plain; charset=utf-8 Hey Andreas, On Fri Feb 20, 2026 at 11:22 AM CET, Andreas K=C3=A4h=C3=A4ri wrote: > Hi, > > A few months ago I asked this question on the "Unix & Linux" > StackExchange site, but without getting a proper answer, other than > a comment saying it's not possible. > > I'm posting it here to see whether anyone has had a similar issue, or > knows of plans to support this in the future, or just in general has > thoughts on the matter. It's not a critical issue for me. > > Assuming I have the following repository configuration: > > http://dl-cdn.alpinelinux.org/alpine/latest-stable/main > http://dl-cdn.alpinelinux.org/alpine/latest-stable/community > > @edge http://dl-cdn.alpinelinux.org/alpine/edge/community > @edge http://dl-cdn.alpinelinux.org/alpine/edge/testing > Please not that this is _very_ unsupported and you _will_ get into issues with this way. Mixing repositories with different Alpine versions is unsupported: https://docs.alpinelinux.org/user-handbook/0.1a/Working/apk= ..html#_repositories_releases_and_mirrors > I usually want to install packages associated with each other under a > common virtual package, e.g., > > apk add -t docker-all docker docker-doc docker-cli-compose > > This works fairly well, but it doesn't work if I want to use the @edge > tag, as in, e.g., > > apk add -t docker-all docker@edge docker-doc@edge docker-cli-compose@edg= e > > This fails with: > > ERROR: 'docker@edge' is not a valid child dependency, format is name([<>= ~=3D]version) > > It would be nice if it were possible to use the tag in this context, as > it would allow me to easily install a set of related packages from a > tagged repository as a common virtual package. This is a known issue, because "virtual packages go to the package database= as locally generated packages. And package dependencies cannot have tags, beca= use tags are local configuration." See .=