[04:56] Eickmeyer[m]: re, installing man pages... It seems we install studio-controls.1 in man1/ but if I look at the installed file it is studio-controls.1.gz [04:58] Eickmeyer[m]: so how did it get from one to the other? There is mention of a mandb command, is that what happens? or is there something else? [04:59] I guess for that matter, if the text is still the same the .gz doesn't matter. Does the man command do the actual formatting? [05:00] I guess it doesn't matter [05:00] Eickmeyer[m]: I think I have answered my own question [05:02] if I just install the raw text the system may at some later time gz it. So I just have to make sure the uninstall command removes studio-controls.* [05:07] OK, so mandb does not seem to compress the file does some other debtool do that? [14:06] FYI, Qt 5.15 is probably going to starting landing in proposed later today [14:17] OvenWerks: Yeah, debhelper does the compression automatically for any manpages it finds. [14:17] RikMills: Good news! [16:10] Eickmeyer[m]: in controls, the lib dir has gone... err well moved to usr/lib [16:10] OvenWerks: Sounds good, should be an easy packaging change once we get to it. [16:11] make install will put everything in /usr/local by default but the usual parameters will put it in /usr... but for deb that is probably not needed because everything is in a tree already [16:12] Only thing is that if dh sees a makefile it'll try using it. [16:13] a makefile saves me having to deal with command line parameters [16:15] Honestly, it shouldn't matter so long as everything ends up where it's supposed to. In the case of dh, it should throw the build into debian/studio-controls, which should get picked-up easily. [16:15] TL;DR: I don't think it'll be a factor [16:16] In fact, it might even eliminate the need for d/studio-controls.install [16:17] It does try to create links where needed [16:17] Which eliminates the need for d/studio-controls.links (if we even have it).