I've created a tfdocgen package now, and modified libticonv to depend on it make install the documentation during the install process. I'll soon do this for all the others as well.
Is it worth the trouble to try to isolate developer-oriented documentation files and bundle them into the *-devel subpackage instead? I doubt it is but I thought I'd check.
I'm not convinced either. At least, it's not a priority
EDIT: Also, is there any extra documentation for either tilp or gfm that should be packaged? Or even for tfdocgen, I suppose?
FWIW, for both GFM and TILP, the documentation installed by the Windows (ISS) installers is a good start.
If not, I think everything is now done from a packaging standpoint.
Good, but now, the code base is not ready (new ROM dumper, libarchive)... and it's too late for me working much on it tonight...
I'll have more time this week-end.
EDIT 2: For the mean time I've disabled the call to desktop-file-validate in the tilp2 and gfm packages.
I've built x86_64 and i386 versions of the packages and put them in a temporary yum repository running on my local server. The repo file for that is available here, and I've edited the first post to have more information about this.
Thanks for your work