1. gtk-doc includes !app-text/xhtml1 as dependency, but xhtml1 doesn't block gtk-doc 2. as far as I can see, xhtml1 & gtk-doc doesn't conflict with each other, so why these blocking dependency? Reproducible: Always Steps to Reproduce: 1. 2. 3.
1.) The blocks are mutual, portage sorts that out. 2.) Satai added these in, for good reason it seems, but I can't find the bugs/reports with the information. Here's the relevant comments from him. ChangeLog: 09 Apr 2003; Matthew J. Turk <satai@gentoo.org> gtk-doc-1.0.ebuild, gtk-doc-0.9-r2.ebuild : Updated to block xhtml1. Problems with that conflicting with anything generated by gtk-doc. CVS comment: Blocking xhtml1. Fixes tons of problems. Briefly mentioned in bug 17628 I've looked even further, and someone has reported that xhtml1 breaks things. So it's now a blocked package by gtk-doc, which has all the problems. I suspect it's to do with the recurring SGML problems. Either way, this isn't a bug.
>1. gtk-doc includes !app-text/xhtml1 as dependency, but xhtml1 doesn't block gtk-doc No. xhtml1 dosn't block gtk-doc, so portage allows me to emerge xhtml1 after gtk-doc and shows me the blocking problem, when I do something like emerge -puD world and not when I emerge xhtml1. If xhtml1 breaks gtk-doc stuff, it should definitely have a !dev-util/gtk-doc dependency. Another point is that I faced the gtk-doc problem mentioned in Bug 17628 a lot, without having xhtml1 installed at all. I don't think these bug is really fixed.
Okay, yep you're right here. Adding the double block, no problem. I only referenced that bug in passing in my effort to find out why there was the initial block, but now I've found out why. xhtml1 causes all sorts of problems with gtk-doc and it really should be blocked. Your two initial questions were 1.) why arent the blocks doubled ? (fixed now) 2.) why are they blocked in the first place. Check out a bug like 32542 for more information on that.
xhtml1 does not need to block gtk-doc because it "works" even if gtk-doc is installed. After all, xhtml1 is just a bunch of files. If the xhtml1 ebuild is broken, fix it. If the xhtml1 source is broken, please file a bug upstream (w3 consortium at www.w3.org). Otherwise, fix gtk-doc if it is broken. Right now, my system and other people's likely as well are partly unusable, so please reopen this bug and adjust severity to major.
This bug is as an alias for #69728, which reports the same thing. IMHO this bug should be re-opened, the problem _does_ still exist.
*** Bug 69728 has been marked as a duplicate of this bug. ***
Okay, I'm re-opening this bug since it seems like the reason why gtk-doc and xhtml block each other was never clear, and apparently there is no valid reason why those packages can't be installed together. If one of them is broken, we should fix that instead of going around the problem with the block. Obz, Could you help us out with this? Can you remember why you mentioned xhtml should really be blocked? I read the discussion at bug #32542 but it looks like in that case the catalogs weren't being updated, and it's still unclear why xhtml was being blamed.
I've removed the mutual block between xhtml1 and gtk-doc. Some remarks: a) The only problems I've seen used as evidence to implement the block (bugs #17628 and #32542) are actually unrelated to xhtml1. b) xhtml1 had some issues of its own, which caused problems with openjade and SGML documents, but they have been fixed by now. c) In any case, if packages like xhtml1 bring more problems, creating blocks is not a good solution. Those bugs should be treated individually and fixed in the related packages. Thank you all for your help on these issues.
