trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: January 2014

Icon conflicts in tdeaddons-tdeartwork-tdesdk (which one to choose?)

From: "David C. Rankin" <drankinatty@...>
Date: Tue, 28 Jan 2014 17:20:12 -0600
Darrell,

  We have run into another icon conflict error. I know some package managers do
not care and will let you overwrite icons, fonts, etc.., but Arch's pacman
package manager will not let you overwrite anything in the filesystem on the
theory that "No package should conflict with another". Of course you can --force
any install and removal, but that defeats the purpose of proper packaging.

  There are a couple of TDE icons that are present in several different
packages. If one package is installed before any other containing the same
icons, then install of the subsequent packages fails. At issue are:

tde-tdeaddons-14.0.0-1-i686.pkg.tar.xz

opt/trinity/share/icons/locolor/32x32/apps/ktimemon.png
opt/trinity/share/icons/locolor/16x16/apps/ktimemon.png

tde-tdeartwork-14.0.0-1-i686.pkg.tar.xz

opt/trinity/share/icons/locolor/32x32/apps/ktimemon.png
opt/trinity/share/icons/locolor/32x32/apps/kbabel.png
opt/trinity/share/icons/locolor/16x16/apps/ktimemon.png
opt/trinity/share/icons/locolor/16x16/apps/kbabel.png

tde-tdesdk-14.0.0-1-i686.pkg.tar.xz

opt/trinity/share/icons/locolor/32x32/apps/kbabel.png
opt/trinity/share/icons/locolor/16x16/apps/kbabel.png

  So this has to be handled from a packaging standpoint on arch. Fortunately,
the package that contains all icons at issue is tdeartwork. For Arch, I will
write conditional checks for tdeaddons and tdesdk to avoid the issue.

  How are the other distros handling this? Can TDE move these conflicting icons
to tdeartwork exclusively.

-- 
David C. Rankin, J.D.,P.E.