[arch-dev-public] Automating package conflict resolution whenever possible (xorgproto/libxfont dependency conflict)

Doug Newgard scimmia at archlinux.org
Wed Feb 14 00:10:06 UTC 2018

On Wed, 14 Feb 2018 00:56:33 +0100
Baptiste Jonglez <baptiste at bitsofnetworks.org> wrote:

> Hi,
> Eli and I disagree about how dependency conflicts should be handled when
> packaging.  This was prompted by the libxfont dependency conflict arising
> from recent xorgproto changes [1].
> My position in this case: it would be really easy to avoid this conflict,
> by adding libxfont to the Replaces() array of xorgproto.  This would cause
> libxfont to be automatically uninstalled upon sysupgrade, which is nice
> because it's an obsolete and now-useless package.

I saw the direct emails before this one, so I'll just quote part of my reply

Replaces is for when packages are renamed, nothing more. That is NOT in any way
what happened here, libxfont and libxfont2 are different libraries. Should GTK3
replace GTK2? Qt5 replace Qt4?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <https://lists.archlinux.org/pipermail/arch-dev-public/attachments/20180213/a27c1f06/attachment.sig>

More information about the arch-dev-public mailing list