It would be nice to have the extract package in portage. It at least depends on xkeyvals.
Ok, it requires the package verbatim (included in tetex), and it requires xkeyval version 2.5. xkeyval-2.4 is included in >=tetex-3.0. Copying over the xkeyval files of tetex-3 with the newer 2.5 version works fine, but is ugly :P For tetex-2 is an xkeyval package in portage, but also only up to version 2.4. Same procedure works here as well.
It usually speeds things up tremendously if you supply an initial ebuild yourself :-) Instructions on how to do so are at: http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml?part=2&chap=1 Most devs don't have time to create new ebuilds for new packages themself, they have enough trouble keeping up to speed with the ones that are already in the portage tree. If you supply an ebuild (possible both for extract and xkeyval) I will be happy to test it.
No ebuild for two months, so i'm closing it. Feel free to reopen the bug if you provide an ebuild.
I wouldn't know how to create an ebuild for this, I actually dont't think it is possible. It would include overwriting the xkeyval files of the current tetex installation. It might be interesting for the next tetex release, so just leave it closed for the next years ;)
You could open a bug for upgrading xkeyval (which is in the tree: dev-tex/xkeyval but at version 2.4 as you mention) and then make an ebuild that depends on the new ebuild for xkeyval. Put in another way: If you make an ebuild for this package that depends on dev-tex/xkeyval-2.5 then i'll upgrade the xkeyval to that version.
Well, xkeyval is included per default in >=tetex-3, but not in the right version. I don't think it is worth the effort, since this would work for tetex-2 only (if at all). For tetex-3 we would actually need to modify the tetex-ebuild, and "patch" xkeyval to a latter version. Thanks, but I think we can just close the bug (it doesn't look like someone else is using it, anyways ;).
