For example when you install the gnome-list with GRP, scrollkeeper-update gets run many times over and over, which is just a waste of time, it would make more sense to set a variable in each packages' post_inst that portage understands and runs scrollkeeper-update only once at the end.
This is a thorny problem, since each ebuild needs to run it if the ebuild updates the scrollkeeper database.. We've trimmed it down so its only run when .omf files are installed, but passing it all over to the end-of-session will not work until a feature in portage supports that. reassigning this to carpaski to hear his comments.
A pleasant way isn't gonna come by anytime soon. At some point, after-the-merges/one-time runs will be possible, but this is definately a holder.
i'm going to close this issue because: 1. the issue isn't scrollkeeper-update really a hog if run in postinst(), which is what happens now. 2. previously, some packages ran scrollkeeper-update during src_install() with bad options, which caused it to regenerate scrollkeeper indexes that were never used. this has now been fixed for most packages with that symptom (mostly gnome ones)
