https://bugzilla.novell.com/show_bug.cgi?id=858842 https://bugzilla.novell.com/show_bug.cgi?id=858842#c4 --- Comment #4 from L. A. Walsh <suse@tlinx.org> 2014-01-16 16:08:48 PST --- (In reply to comment #3)
1) the one you mention where the entire cache is rebuilt with each font installed: pointless. It should should be done, at MOST, once -- if user is
Correct. This is related to dropping suseconfig.* scripts, see bug 773575 for details.
2) 2nd bug doubling the pain is only on 64-bit systems. Linda, please stop discussing this in three different bugs. Thanks.
Please realize the fix you claim is in for 13.2 doesn't fix issue #2 nor does it address issue/bug #856476. fc-cache will still be run twice -- for 32&64 bit archs (#2) fc-cache runs synchronously in foreground as regular user and again as root, taking ~5 minutes each each time the /usr/share/fonts dir is touched (which is often as my font-libs are 3-way synchronized between machines). (bug856476) Having been dealt with QA for decades and having been in QA -- bug reporters are always advised NOT to combine bugs unless they absolutely know they are the same root cause --- In this case, you have advised me not to file 3 separate bugs because you don't seem to realize that the other two issues won't be solved by rpm post-install scripts being accumulated into suseconfig-post install scripts. On top of that -- suseconfig has had this bug in the past when they were rolled in -- If I installed a new font via rpm, I had to wait through a suse config for tex-caching scripts -- which I never used (and have attempted to make sure are not on my system (unless I am specifically using them)). The bug "fix" you think solves the other 2 issues mentioned, doesn't. And the fix you think fixes it is itself a problem in the same class as bug856476 -- updating all that stuff in foreground while the user is waiting). Please don't presume that a user describing 3 or more different problems with a product should roll all the problems into 1 bug. That's not good QA practice. all be rolled into 1 bug -- it helps things get lost. Example: if someone presumed that a mitigation fix for this bug (moving the cache runs into 1 run) would also, automatically address #2 (bug #853225), and bug #856476 (running fc-cache for regular users and root separate -- and making both wait, synchronously when usually not needed), then those bugs might not get addressed or be marked as "low priority".... ;-) -- 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.