Pin omarchy-settings dependency to exact pkgver
omarchy-settings-dev provides omarchy-settings (unversioned), so an
unversioned dependency let the dev package satisfy stable omarchy's
settings requirement, allowing a mixed dev/stable install. A versioned
dependency (omarchy-settings=${pkgver}) can only be satisfied by the
real settings package from the same pinned commit and forces the pair
to upgrade together. Verified: requesting only omarchy on a system with
the -dev pair installed replaces both with the stable pair.
This commit is contained in:
@@ -24,7 +24,12 @@ conflicts=('omarchy-dev')
|
||||
depends=(
|
||||
# Omarchy meta
|
||||
'omarchy-keyring'
|
||||
'omarchy-settings'
|
||||
# Exact-version pin: omarchy-settings-dev `provides=omarchy-settings`
|
||||
# (unversioned), and an unversioned dependency here would let the dev
|
||||
# package satisfy it, leaving a mixed dev/stable install. A versioned
|
||||
# dependency can only be satisfied by the real omarchy-settings built
|
||||
# from the same _commit, and forces the pair to upgrade together.
|
||||
"omarchy-settings=${pkgver}"
|
||||
|
||||
# Bootloader stack. Lives here rather than on omarchy-settings because
|
||||
# omarchy-settings is also installed into the live ISO env (for plymouth
|
||||
|
||||
Reference in New Issue
Block a user