On Monday, September 23, 2013, Kevin Ottens wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Saturday 21 September 2013 15:25:27 Albert Astals Cid wrote:<br>
> El Dissabte, 21 de setembre de 2013, a les 11:15:52, Stephen Kelly va<br>
><br>
> escriure:<br>
> > Albert Astals Cid wrote:</blockquote><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
> > >> > Anyway as I was chatting with Aleix yesterday, kdoctools being a<br>
> > >> > tier1<br>
> > >> > framework "is not enough" since kconfig has docbook files (e.g. man<br>
> > >> > page of kconfig_compiler) so we need a tier0 here ;-)<br>
> > >><br>
> > >> Where is kconfig now?<br>
> > ><br>
> > > Do I really need to do an ls for you?<br>
> ><br>
> > What I was trying to get at is that you seem to be implying that kconfig<br>
> > depends on kdoctools (ie, a tier1 depends on a tier2), therefore kdoctools<br>
> > can't be tier1. I don't follow that logic.<br>
><br>
> Well, kconfig depends on kdoctools because as I said there is a docbook for<br>
> the kconfig_compiler manpage.<br>
><br>
> So yes, there is a tier1 that depends on a tier2. That if as I understand we<br>
> plan to ship the kconfig_compiler manpage together with the kconfig<br>
> framework tarball.<br>
<br>
Well, I'm not sure we want to do that. This docbook seems useful only because<br>
kconfig_compiler --help does a poor job at documenting itself. So what about<br>
completing kconfig_compiler --help output to make it useful and get rid of the<br>
docbook?<br>
<br>
To me it looks like most of the docbook files in kdelibs are pretty much in<br>
the same situation and I'd favor proper --help support there than adding a<br>
dependency on kdoctool.<br>
</blockquote><div><br></div><div>I assume making it an optional dependency (if not present, don't build the manpage) doesn't help, because the current tiers fully allow having kdoctools depend on kconfig, which would cause a circular dependency.</div>
<div><br></div><div>What does kdoctools buy us here? Maybe we can use a third-party docbook<span></span></div><br><br>-- <br>Nicolás<br>