On Fri, 01 Jul 2016, Mauro Carvalho Chehab <mchehab@xxxxxxxxxxxxxxx> wrote: > Not being able to compile just one docbook is a regression and breaks > my process. This needs to be fixed. Do you have a regression with *DocBook XML* on docs-next now? If yes, clearly that must be fixed ASAP. As to Sphinx, I fear your DocBook workflows are so elaborate that we are bound to break some of them when switching over. Personally, I don't think that's all bad. It's an opportunity to make things better. But we can't make all of that happen overnight for media. This is why we have Sphinx and DocBook side by side for now. We specifically wanted to make the switch for e.g. GPU documentation fast, act as guinea pigs, hit the issues, and make it easier for others in the end. We'd also love to get some of those validation things you have, for everyone, but using Sphinx instead of a bunch of scripts and sed on the input files. This is also one of the reasons why I so much want to keep everything behind one configuration file, and build everything in the Sphinx toolchain. To keep it all more uniform, to not duplicate stuff, and not deviate to some silos like we've done in the past. I think when we have things working, we can add dedicated config files for the select few things that have additional special needs. Media is probably one of them. But that said, I think we should be able to keep including that to the main documentation build too. Also, many thanks for digging into this and reporting issues that you do face. BR, Jani. -- Jani Nikula, Intel Open Source Technology Center -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
