>pkg_postinst() { > ewarn "To allow parallel installation of sig++-1.0, sig++-1.2, and sig++2.0" > ewarn "the header files are now installed in a version specific" > ewarn "subdirectory. Be sure to unmerge any libsig++ versions" > ewarn "< 1.0.4 that you may have previously installed." >} libsigc++ ebuild could detect if user really has installed <libsigc++-1.0.4 using has_version and provide more targeted information like "you have old version of libsigc++ installed. Please update it to ... (some newer version)." or not display this "Be sure to ..." warning. In my opinion it would more convenient and clear for the user.
It's not really needed. All libsigc++ versions are properly slotted and users should never have to worry about updating to or from a specific version. If a package in portage incorrectly pulls libsigc++, a bug should be filed against that package. With the slotted deps in EAPI=1, this is now really easy to do. Thanks
