https://bugzilla.novell.com/show_bug.cgi?id=365649 User jkupec@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=365649#c1 Ján Kupec changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jkupec@novell.com, sbrabec@novell.com --- Comment #1 from Ján Kupec 2008-02-28 10:40:26 MST --- I fear running suseconfig after each zypper install command (running it after an update or dist-upgrade would be more acceptable). Why are these things not handled in the package scripts? Running suseconfig for _any_ package install/update/remove seems like quite an annoyance for me. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=365649 User wberrier@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=365649#c3 Wade Berrier changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jpr@novell.com --- Comment #3 from Wade Berrier 2008-02-28 11:41:08 MST --- JPR, what's your take on this? I ran into this specifically with monodevelop, which changes from using icons in /usr/share/pixmaps to /usr/share/icons. So upgrading from one version to the next breaks unless you run SuSEconfig to update the icon cache. I couldn't find any other packages updating the icon cache from a spec file. (Plus, if SuSEconfig is going to get run after you install packages in yast, you wouldn't want to run it during install anyways). Side note: What would be really sweet is to have a way in the .spec file that would queue up which SuSEconfig modules should be run after all packages are installed, and only run those. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=365649 User wberrier@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=365649#c5 --- Comment #5 from Wade Berrier 2008-02-28 13:00:37 MST --- (In reply to comment #4 from Ján Kupec)

(In reply to comment #3 from Wade Berrier)

...

Side note: What would be really sweet is to have a way in the .spec file that would queue up which SuSEconfig modules should be run after all packages are installed, and only run those.

That's exactly my point. Running suseconfig every time would very much affect user's experience of zypper in a negative way. Running it selectively is very desirable.

Agreed. (I've heard rumors about doing something like this, but I can't find any traces.)

The situation in YaST is a bit different from user's POV - you can browse through the packages, select/unselect them randomly and after you're finished, you click to install them all at once. There is a smaller chance that you will want to choose a few, install, choose another, install, etc. But with zypper the chance is bigger.

The main issue is that installing packages with yast versus zypper gives different results. Maybe even a note after zypper install saying, "You should probably run SuSEconfig manually" ? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=365649 User crrodriguez@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=365649#c7 Cristian Rodriguez changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |crrodriguez@novell.com --- Comment #7 from Cristian Rodriguez 2008-02-28 16:27:33 MST --- (In reply to comment #5 from Wade Berrier)

The main issue is that installing packages with yast versus zypper gives different results. Maybe even a note after zypper install saying, "You should probably run SuSEconfig manually" ?

SuSEconfig is deprecated and I cant make much sense on making it to run on every package install , isnt the %run_suseconfig macro enough to accomplish this task ? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=365649 User crrodriguez@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=365649#c9 --- Comment #9 from Cristian Rodriguez 2008-02-28 17:02:57 MST --- (In reply to comment #8 from Wade Berrier)

Ah, I didn't know about that macro, although maybe that's what I'd heard about before? Thanks!

Yes, we need documentation, for usage you can read the source ;) /usr/lib/rpm/suse_macros -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=365649 User vuntz@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=365649#c11 --- Comment #11 from Vincent Untz 2008-02-29 02:17:35 MST --- Just wondering: if I install many packages using %run_suseconfig, will all of them do the call or will it be done only once at the end of the zypper run? If I read it correctly, it seems it's the former. The latter would make things a bit faster. I can open another bug if there's interest in implementing this. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=365649 User visnov@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=365649#c13 --- Comment #13 from Stanislav Visnovsky 2008-02-29 03:16:08 MST --- Usage of SUSEconfig is deprecated. I know it can bring quite some speedup, but the first approach is to fix packages. I see no need for implementing support to run SUSEconfig in zypper. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=365649 User visnov@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=365649#c15 --- Comment #15 from Stanislav Visnovsky 2008-02-29 04:31:57 MST --- Or fix gtk-icon-cache? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=365649 User sbrabec@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=365649#c17 --- Comment #17 from Stanislav Brabec 2008-02-29 05:28:00 MST --- Well, there is another solution, at least for icon cache: - Patch gtk to search icon everywhere, if it is not found in cache. - Add gtk-update-icon-cache to cron-weekly. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=365649 User sbrabec@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=365649#c19 --- Comment #19 from Stanislav Brabec 2008-02-29 06:18:35 MST ---

...

- Patch gtk to search icon everywhere, if it is not found in cache. Will have an impact on performance.

Yes, it will. Icon lookup may require to check 530 directories: find /usr/share/icons/hicolor /usr/share/icons/gnome /usr/share/icons/Tango -type d | wc -l 529

I'm not an expert, but triggers do look like the right solution.

These triggers don't exist yet (Depending on opinion of RPM developers, they will or will not appear in future. It's implementation is not popular, as it would require to check all symbols, not only package names.) Maybe it is possible to move this function to libzypp - simply keep SuSEconfig scripts as they are, and change a way they are called: directory /etc/zypper-conf.d: gtk2.conf: final_trigger_recursive /usr/share/icons /sbin/conf.d/SuSEconfig.gtk2 desktop-file-utils.conf: final_trigger /usr/share/applications/*.desktop /sbin/conf.d/SuSEconfig.desktop-file-utils gnome-vfs2.conf: final_trigger /usr/share/applications/*.desktop /sbin/conf.d/SuSEconfig.gnome-vfs2 It can even be extended with other similar use cases: fonts.conf: final_trigger_recursive /usr/share/fonts /sbin/conf.d/SuSEconfig.fonts glibc.conf: transaction_trigger /lib/*.so* /sbin/ldconfig transaction_trigger /usr/lib/*.so* /sbin/ldconfig transaction_trigger /opt/*/lib/*.so* /sbin/ldconfig -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=365649 User sbrabec@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=365649#c21 --- Comment #21 from Stanislav Brabec 2008-03-03 04:46:09 MST --- They either don't do it correctly (i. e. they don't run it for kdebase3 and similar packages, sou they enter into cross-desktop breakage - not displaying KDE apps correctly in GNOME menu) or they ignore installation time issue. On slower systems with a lot of installed packages, gtk-icon-cache-update may take ~15 secs per run. Note: We did this in past for fonts. On slow machines it caused few additional hours of installation time. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=365649 User sbrabec@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=365649#c23 --- Comment #23 from Stanislav Brabec 2008-03-04 07:05:11 MST --- No. Abusing of -p rpm script parameter saves only few milliseconds by saying: "Use /sbin/ldconfig to interpret this empty script" instead of: "Start shell interpreter and run a script containing /sbin/ldconfig." And even this would be impossible for KDE apps. Using for it only RPM features, they would need: %post if test -x /usr/bin/gtk-update-icon-cache ; then /usr/bin/gtk-update-icon-cache fi %postun if test -x /usr/bin/gtk-update-icon-cache ; then /usr/bin/gtk-update-icon-cache fi Or a bit more effective with newer RPM: %posttrans if test -x /usr/bin/gtk-update-icon-cache ; then /usr/bin/gtk-update-icon-cache fi %postun if test "$1" = 0 ; then if test -x /usr/bin/gtk-update-icon-cache ; then /usr/bin/gtk-update-icon-cache fi fi -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=365649 User wberrier@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=365649#c25 --- Comment #25 from Wade Berrier 2008-03-05 15:25:02 MST --- (In reply to comment #24 from JP Rosevear)

Ok, the problem is though that given we are trying to deprecate SuSEconfig, it seems odd to go back and add it to all the necessary .spec files.

+1 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=365649 User schubi@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=365649#c27 Stefan Schubert changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |schubi@novell.com Component|libzypp |GNOME --- Comment #27 from Stefan Schubert 2008-04-25 02:40:05 MST --- It is not a libzypp issue anymore ;-) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=365649 User sbrabec@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=365649#c29 --- Comment #29 from Stanislav Brabec 2008-05-05 11:07:15 MST --- It's deprecated. Preferred way is the rpm scriptlet. But rpm scriptlets are much less efficient, as they have to be started twice per each affected package instead of once per the whole installation. It does not hurt for scripts, which are fast enough to be started 1000 times during upgrade (e. g. /sbin/ldconfig), or those, which are rare enough to be started only by ~10 packages (e. g. pango modules list or update-mime-database). For scripts, which are slow (~10 sec) and affect hundreds of packages (e. g. gtk-update-icon-cache, update-desktop-database), it would cause unacceptable installation time: Example: On a typical installation, desktop files belong to ~150 packages. Each of these packages outdates gtk-icon-cache and desktop-database. Each gtk-update-icon-cache run needs to scan ~700 directories. On an avarage machine, which does not have all these directories in the cache, the run takes ~10 sec. Now compute the cost of leaving of the deprecated SuSEconfig: With SuSEconfig: Running gtk-update-icon-cache needs ~10 sec for the whole distribution upgrade. With rpm scripts: Running gtk-update-icon-cache needs ~3000 sec for the whole distribution upgrade (10x150x2). Summary: Move to "clean" rpm based solution makes 30000% performance loss in this particular case! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=365649 User locilka@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=365649#c31 Lukas Ocilka changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |locilka@novell.com --- Comment #31 from Lukas Ocilka 2008-05-28 07:17:29 MDT --- See bug 365649, gtk-update-icon-cache is called during installation (fist stage) of packages and uses about 54 MB RAM. We want to lower the memory requirements, not to increase them. For installation, there might be a single run of that script at the end and it doesn't need to be in SuSEconfig at all. Just in installation scripts. The cases are on a running system already and don't suffer from the lack of free RAM. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=365649 User coolo@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=365649#c33 Stephan Kulow changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |coolo@novell.com --- Comment #33 from Stephan Kulow 2008-05-28 08:37:28 MDT --- why track this issue in two bugs? My comment is in https://bugzilla.novell.com/show_bug.cgi?id=365649#c32 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=365649 User casualprogrammer@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=365649#c35 Casual J. Programmer changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |casualprogrammer@gmail.com --- Comment #35 from Casual J. Programmer 2008-06-11 12:31:39 MDT --- Not sure where this discussion leads. As far as I perceive it, something needs to be done after installation. Comment #26 makes a good point: as long as packages should be installable by rpm -i | -U this needs to be fixed in the package itself. Zypper then picks up from there as well as yast2, I should expect. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=365649 User wberrier@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=365649#c37 Wade Berrier changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|wberrier@novell.com |dmacvicar@novell.com --- Comment #37 from Wade Berrier 2008-06-20 16:39:11 MDT --- Not sure how this got assigned to me... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=365649 User vuntz@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=365649#c39 --- Comment #39 from Vincent Untz 2008-11-19 15:37:30 MST --- *** Bug 446706 has been marked as a duplicate of this bug. *** https://bugzilla.novell.com/show_bug.cgi?id=446706 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=365649 User vuntz@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=365649#c41 Vincent Untz changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |FEATURE --- Comment #41 from Vincent Untz 2008-11-19 15:43:19 MST --- closing as FEATURE -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=365649 User crivera@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=365649#c43 Chris Rivera changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |glunardi@novell.com --- Comment #43 from Chris Rivera 2009-01-15 12:09:19 MST --- *** Bug 462653 has been marked as a duplicate of this bug. *** https://bugzilla.novell.com/show_bug.cgi?id=462653 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.