Having done a complete install from scratch I found that /var/lib/scrollkeeper contains links to /var/tmp/portage/gdm-2.2.5.4/image//var/lib/scrollkeeper/image, which is clearly not a good thing. Additionally, it might be a good idea to investigate how to really work with scrollkeeper and a packagemanagement system : * I don't really know what is stored in /var/lib/scrollkeeper, but scrollkeeper seems to modify files when new applications are installed. Should these modifications remain when a package is uninstalled or be undone? * How should binary packages be shipped? * Should ebuilds be allowed to modify /var/lib/scrollkeeper directly and thus create/modify non temporary files outside of the image dir?
This has been on my todo-list for quite some time. I'll try to get around to it soon.
Hi! Don't know if this is useful to you, but I am attaching a sandbox log file of scrollkeeper violations that occured when merging scrollkeeper-0.2-r1.eebuild. tod
*** Bug 153 has been marked as a duplicate of this bug. ***
GDM seems to be the only package that does this really wrong (since they have stuff in /var/lib/scrollkeeper) in it's CONTENTS-file. No package should touch /var/lib/scrollkeeper during src_install. Everything inthere is autogenerated by scrollkeeper-update (which should be called in pkg_postinst and pkg_postrm for packages that use scrollkeeper).
problem is that the packages run scrollkeeper-update -p /var/lib/scrollkeeper in there "make install"-phase. I'm going to grab the author/maintainer of scrollkeeper to ask him about this. This can't be right, (non-package based distributions but not for package-based).
Here is what should fix most of the ebuilds. cd omf-install cp Makefile Makefile.old sed -e "s:scrollkeeper-update.*::g" Makefile.old > Makefile rm Makefile.old cd ${S}
You wanna create a bash function in ebuild for that? Might be handy.
That might be an idea. What do you think about that drobbins? prepare_scrollkeeper (or something?)
evolution, gdm and gnome-utils fixed.
scrollkeeper itself is also updated now.
So this bug can be considered fixed then? You added something to portage for scrollkeeper support?
gnome-extra/gnome-db also fixed.
the issue is resolved, just have to track down the packages that are doing wrong.