From fbcc0d8b8b03bd4d351e45aba8e701d68c93c1a7 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Pablo=20Correa=20G=C3=B3mez?= Date: Mon, 17 Aug 2026 13:58:48 +0200 Subject: [PATCH] docs: make the alsa-ucm-conf packaging bug as resolved Part-of: --- docs/packaging.md | 20 ++++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/docs/packaging.md b/docs/packaging.md index 47ad2b988..fa7b84b4d 100644 --- a/docs/packaging.md +++ b/docs/packaging.md @@ -270,8 +270,8 @@ without a version, but given that one is versioned would still conflict. For example. :::{warning} -The example below shows a packaging bug. Forks should have never used virtual -providers! This is helpful to showcase this common pitfall +The example below shows a (former) packaging bug. Forks should have never used +virtual providers! This is helpful to showcase this common pitfall ::: ```sh @@ -324,14 +324,14 @@ only in some specific circumstances? In those situations we have to: are other constraints (like the device package dependency on the fork). * If the fork has an equal or higher version that then original package, however, we might bump into the situation that installs that shouldn't have - the fork still get it installed due to the higher version. The solution to - that problem is to force a dependency on the non-forked version in a common - package used by most users. For example, `postmarketos-ui-gnome` added - `!gnome-shell-mobile` to avoid regular installs getting the mobile versions. - Sometimes, however, this gets complicated due to the fact that the provider - is the name of the original package (like in the case of `alsa-ucm-conf` - above). In those situations, it might be needed to introduce an alternative - versioned provider to disambiguate (e.g: + the fork still get it installed due to the higher version. The easiest + solution to that problem is to force a dependency on the non-forked version + in a common package used by most users. For example, `postmarketos-ui-gnome` + added `!gnome-shell-mobile` to avoid regular installs getting the mobile + versions. Sometimes, however, this gets complicated due to the fact that + the provider is the name of the original package (like in the case of + `alsa-ucm-conf` above). In those situations, it might be needed to introduce + an alternative versioned provider to disambiguate (e.g: `provides="audio-conf=$pkgver-r$pkgrel"`), or to force the forked packages to provide a lower version than the other package.