On Tue, Sep 24, 2013 at 2:09 PM, Kevin Ottens <er...@kde.org> wrote:
> On Tuesday 24 September 2013 13:48:55 Albert Astals Cid wrote: > > El Dimarts, 24 de setembre de 2013, a les 08:49:20, Kevin Ottens va > escriure: > > > On Monday 23 September 2013 13:09:05 Nicolás Alvarez wrote: > > > > Maybe we can use a third-party docbook-to-manpage conversion tool. On > > > > Linux > > > > it would be easy to install, and on Windows it wouldn't be needed > > > > ("what's > > > > a manpage?"). And still leave it optional everywhere... > > > > > > Thats a very good question. Maybe in that case kdoctools is indeed > > > overkill. Someone would have to investigate if something else could be > > > used though. > > That's really weird, we have a solution that works, and you want to use > > something else? > > > > What does that gives us? > > > > That stuff in kde now depends in two docbook-to-manpage conversion tools > > instead of one? > > > > Are you sure that's an improvement? > > Well, as highlighted we have a dependency issue there, so it's either: > 1) no docbook in tier 1 and tier 2 frameworks; > 2) we use a different docbook to manpage tool for tier 1 and tier 2 > frameworks. > > Pick your poison. But we can't keep said dependency issue. > > Regards. > -- > Kévin Ottens, http://ervin.ipsquad.net > > Sponsored by KDAB to work on KDE Frameworks > KDAB - proud supporter of KDE, http://www.kdab.com > > > _______________________________________________ > Kde-frameworks-devel mailing list > Kde-frameworks-devel@kde.org > https://mail.kde.org/mailman/listinfo/kde-frameworks-devel > > Maybe we can bundle the generated documentation? I think we're making it more of a problem than actually is... Maybe the problem here is considering kdoctools as a framework instead of a tool set. Aleix
_______________________________________________ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel