Home_greyopenFATE - openSUSE feature tracking > #309370
Dashboard | Search | Sign up | Login

Please login or register to be able to edit or vote this feature.

Get rid of SuSEconfig.gtk2

Feature state

openSUSE Distribution
Done

Description

There are a few packages which needs a SuSEconfig.gtk2 run afterwards. Currently they touch "run-gtk" and the next SuSEconfig run will execute the script. But the problem is, that only YaST2 calls SuSEconfig afterwards, zypper and rpm do not.

As result, if you install gtk based applications the first time with zypper or rpm, this ones are often broken and don't work. The workaround is, that all this applications get a %run_suseconfig macro. This is very error prone, and makes the installation slower than doing it right from the beginning and let the post install of this packages, which really installs a plugin, register it correct.

As all the bug reports with SLE11 SP1 shows, the current solution is not maintainable in any ways. We need to get rid of this hack.

User benefit:

Make gtk applications work out of the box again and not depending on a special Novell hack not supported by most of our own RPMs and 3rd party RPMs.

Relations

Discussion


icons/user_comment.png J. E. wrote: (7 years ago)

Correctness before speed, though, so the ultimately short solution is to just run SuSEconfig in %post, like it's done for fonts. Does our rpm have triggers/post-after-transaction yet?

icons/user_comment.png V. U. wrote: (7 years ago)

We got rid of this in 11.4. Packages now call %icon_theme_cache_post/postun in %post/%postun (and I fixed all GNOME packages to do that). And when a new rpm will fix this for us, we'll be able to update the macros.

Last change: 5 years ago
Voting
Score: 9
  • Negative: 0
  • Neutral: 0
  • Positive: 9
Tags
Feature Export
Application-xmlXML   Text-x-logPlaintext   PrinterPrint