(Merging replies.) On 06/28/2016 08:35 AM, Andreas Tille wrote: > On Mon, Jun 27, 2016 at 11:57:12PM +0200, Christian Seiler wrote: >> [Multi-Arch] >> In your package, that's already the case, so you can just add the header >> to debian/control. > > A, well, yes - I simply forgot this. In my initial question I assumed > something more on the Build-System would be needed.
Well, even if the build system doesn't support --libdir= or similar, you can still install the files in the proper locations manually (via debian/rules directly, .install files, d-shlibmove, or similar); only for very, very few packages does Multi-Arch actually affect the upstream code itself. (Think compilers etc.) (Btw. you still didn't update debian/control in git. ;-)) >> Anyway: in case you want to know more about autoconf/automake etc. >> I would really recommend <https://autotools.io/index.html> in >> addition to the official documentation of that ecosystem ([1], >> [2], [3], [4]). > > I know I should know more about these tools but I need to quite rarely > and the good thing on Debian Mentors is that you (obviously) get > brilliant help if needed. While beeing really great this on the other > hand decreases the motivation to learn everything be heart. ;-) Well, but the reason you get help here is so you can learn from it. ;-) And you don't have to be an expert in the autotools (while I do know quite a bit, I certainly am not), but if you're packaging stuff that uses autotools in Debian (and you're packaging quite a lot of packages that fall in that category), it is really helpful to have an idea about the basics. I would therefore really encourage you to do at least a bit of reading on that topic. > On Mon, Jun 27, 2016 at 10:41:28PM +0200, Christian Seiler wrote: >> On 06/27/2016 07:49 PM, Christian Seiler wrote: >>> Other comments regarding the package: >> >> Oh btw. I just noticed that you don't install the manpage for >> the library function in the -dev package (because d-shlibmove >> doesn't care about manpages, and you don't have an .install >> file for that package). Since upstream includes the manpage, >> I would recommend also shipping it. > > The manpage is not installed since it has zero bytes. (I actially > had a debian/manpages file written but removed it afterwards.) Oh, I didn't check that. Funny that upstream ships it then. In that case, I do agree with your decision not to include it. ;-) Regards, Christian
