[New: openFATE 309370] Get ride of SuSEconfig.gtk2
Feature added by: Thorsten Kukuk (kukuk) Feature #309370, revision 1 Title: Get ride of SuSEconfig.gtk2 openSUSE-11.3: New Priority Requester: Mandatory Requested by: Thorsten Kukuk (kukuk) Partner organization: openSUSE.org 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 ride of this hack. Business case (Partner benefit): openSUSE.org: 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. -- openSUSE Feature: https://features.opensuse.org/309370
Feature changed by: Jan Engelhardt (jengelh) Feature #309370, revision 2 Title: Get ride of SuSEconfig.gtk2 openSUSE-11.3: New Priority Requester: Mandatory Requested by: Thorsten Kukuk (kukuk) Partner organization: openSUSE.org 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 ride of this hack. Business case (Partner benefit): openSUSE.org: 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. + Discussion: + #1: Jan Engelhardt (jengelh) (2010-05-06 23:04:18) + 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? -- openSUSE Feature: https://features.opensuse.org/309370
Feature changed by: Rajko Matovic (rajko_m) Feature #309370, revision 3 Title: Get ride of SuSEconfig.gtk2 openSUSE-11.3: New Priority Requester: Mandatory Requested by: Thorsten Kukuk (kukuk) Partner organization: openSUSE.org 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 ride of this hack. + not maintainable in any ways. We need to get rid of this hack. Business case (Partner benefit): openSUSE.org: 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. Discussion: #1: Jan Engelhardt (jengelh) (2010-05-06 23:04:18) 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? -- openSUSE Feature: https://features.opensuse.org/309370
Feature changed by: Rajko Matovic (rajko_m) Feature #309370, revision 4 - Title: Get ride of SuSEconfig.gtk2 + Title: Get rid of SuSEconfig.gtk2 openSUSE-11.3: New Priority Requester: Mandatory Requested by: Thorsten Kukuk (kukuk) Partner organization: openSUSE.org 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. Business case (Partner benefit): openSUSE.org: 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. Discussion: #1: Jan Engelhardt (jengelh) (2010-05-06 23:04:18) 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? -- openSUSE Feature: https://features.opensuse.org/309370
Feature changed by: Thomas Schmidt (digitaltomm) Feature #309370, revision 6 Title: Get rid of SuSEconfig.gtk2 - openSUSE-11.3: New + openSUSE Distribution: New Priority Requester: Mandatory Requested by: Thorsten Kukuk (kukuk) Product Manager: (Novell) Product Manager: (Novell) Product Manager: (Novell) Project Manager: (Novell) Partner organization: openSUSE.org 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. Business case (Partner benefit): openSUSE.org: 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. Discussion: #1: Jan Engelhardt (jengelh) (2010-05-06 23:04:18) 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? -- openSUSE Feature: https://features.opensuse.org/309370
Feature changed by: Vincent Untz (vuntz) Feature #309370, revision 9 Title: Get rid of SuSEconfig.gtk2 - openSUSE Distribution: New + openSUSE Distribution: Done Priority Requester: Mandatory Requested by: Thorsten Kukuk (kukuk) Product Manager: (Novell) Product Manager: (Novell) Product Manager: (Novell) Project Manager: (Novell) Partner organization: openSUSE.org 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. Business case (Partner benefit): openSUSE.org: 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. Discussion: #1: Jan Engelhardt (jengelh) (2010-05-06 23:04:18) 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? + #3: Vincent Untz (vuntz) (2011-02-22 09:24:39) + 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. -- openSUSE Feature: https://features.opensuse.org/309370
Feature changed by: Stefan Behlert (sbehlert) Feature #309370, revision 10 Title: Get rid of SuSEconfig.gtk2 openSUSE Distribution: Done Priority Requester: Mandatory Requested by: Thorsten Kukuk (kukuk) Product Manager: (Novell) Product Manager: (Novell) Product Manager: (Novell) + Product Manager: (Novell) Project Manager: (Novell) + Engineering Manager: (Novell) Partner organization: openSUSE.org 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. Business case (Partner benefit): openSUSE.org: 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. Discussion: #1: Jan Engelhardt (jengelh) (2010-05-06 23:04:18) 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? #3: Vincent Untz (vuntz) (2011-02-22 09:24:39) 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. -- openSUSE Feature: https://features.opensuse.org/309370
Feature changed by: Stefan Behlert (sbehlert) Feature #309370, revision 11 Title: Get rid of SuSEconfig.gtk2 openSUSE Distribution: Done Priority Requester: Mandatory + Info Provider: (Novell) + Info Provider: (Novell) Requested by: Thorsten Kukuk (kukuk) Product Manager: (Novell) Product Manager: (Novell) Product Manager: (Novell) Product Manager: (Novell) Project Manager: (Novell) Engineering Manager: (Novell) Partner organization: openSUSE.org 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. Business case (Partner benefit): openSUSE.org: 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. Discussion: #1: Jan Engelhardt (jengelh) (2010-05-06 23:04:18) 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? #3: Vincent Untz (vuntz) (2011-02-22 09:24:39) 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. -- openSUSE Feature: https://features.opensuse.org/309370
Feature changed by: Gerald Pfeifer (GeraldPfeifer) Feature #309370, revision 12 Title: Get rid of SuSEconfig.gtk2 openSUSE Distribution: Done Priority Requester: Mandatory Info Provider: (Novell) - Info Provider: (Novell) Requested by: Thorsten Kukuk (kukuk) Product Manager: (Novell) Product Manager: (Novell) Product Manager: (Novell) - Product Manager: (Novell) Project Manager: (Novell) Engineering Manager: (Novell) Partner organization: openSUSE.org 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. Business case (Partner benefit): openSUSE.org: 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. Discussion: #1: Jan Engelhardt (jengelh) (2010-05-06 23:04:18) 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? #3: Vincent Untz (vuntz) (2011-02-22 09:24:39) 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. -- openSUSE Feature: https://features.opensuse.org/309370
Feature changed by: Gerald Pfeifer (GeraldPfeifer) Feature #309370, revision 13 Title: Get rid of SuSEconfig.gtk2 openSUSE Distribution: Done Priority Requester: Mandatory Info Provider: (Novell) Requested by: Thorsten Kukuk (kukuk) Product Manager: (Novell) Product Manager: (Novell) - Product Manager: (Novell) Project Manager: (Novell) Engineering Manager: (Novell) Partner organization: openSUSE.org 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. Business case (Partner benefit): openSUSE.org: 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. Discussion: #1: Jan Engelhardt (jengelh) (2010-05-06 23:04:18) 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? #3: Vincent Untz (vuntz) (2011-02-22 09:24:39) 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. -- openSUSE Feature: https://features.opensuse.org/309370
Feature changed by: Matthias Eckermann (mge1512) Feature #309370, revision 15 Title: Get rid of SuSEconfig.gtk2 openSUSE Distribution: Done Priority Requester: Mandatory - Info Provider: (Novell) Requested by: Thorsten Kukuk (kukuk) Product Manager: (Novell) Product Manager: (Novell) Project Manager: (Novell) Engineering Manager: (Novell) Partner organization: openSUSE.org 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. Business case (Partner benefit): openSUSE.org: 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. Discussion: #1: Jan Engelhardt (jengelh) (2010-05-06 23:04:18) 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? #3: Vincent Untz (vuntz) (2011-02-22 09:24:39) 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. -- openSUSE Feature: https://features.opensuse.org/309370
Feature changed by: Andreas Jaeger (a_jaeger) Feature #309370, revision 18 Title: Get rid of SuSEconfig.gtk2 openSUSE Distribution: Done Priority Requester: Mandatory Requested by: Thorsten Kukuk (kukuk) Partner organization: openSUSE.org 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. + Relations: + - Remove SuSEconfig (feature/id: 100011) Business case (Partner benefit): openSUSE.org: 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. Discussion: #1: Jan Engelhardt (jengelh) (2010-05-06 23:04:18) 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? #3: Vincent Untz (vuntz) (2011-02-22 09:24:39) 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. -- openSUSE Feature: https://features.opensuse.org/309370
participants (1)
-
fate_noreply＠suse.de