When installing PowerDNS (2.9.21 in my case) using the ebuild no header files are installed into the system. Normally that would be ok, since what's the use for headers on a server. But Gentoo puts them always onto the machine (hm, perhaps some USE-flags someday when using binary packages? ;-) ) I expected them to be there too when writing my own backend library for it. It's nothing severe since I can extract the PDNS archive manually into my building directory. But it's a little annoyance and not usual when using Gentoo. Reproducible: Always Steps to Reproduce: 1. emerge pdns 2. q list pdns Actual Results: There are only the binaries, some docs and the init/config file installed. No headers are brought into the system. Expected Results: I would expect the powerdns .hh-files to be in /usr/include or /usr/include/pdns.
There's no powerdns anywhere...
I'm confused. What do you mean by that? I double checked and it's not in any overlay but in the regular portage (and that's great ;-) ). After thinking again I think you thought (thoughtfull, eh? *g*) the packagename would be "powerdns" and not "pdns" (as shown in "Steps to Reproduce")? That's a valid argument, I'd prefer "powerdns" as name too since in the filesystem the full name is used (see /usr/lib/powerdns). But currently it is named pdns. I reopened the bug, hoping this was our misunderstanding. Feel free to close it again if you meant something else.
(In reply to comment #2) > I'm confused. What do you mean by that? I mean that there's no ebuild named powerdns anywhere. So please stick with existing ebuild names in bugs.
OK, development headers are now installed into /usr/include/pdns. I have chosen pdns here, because that's what the other pdns modules use (#include <pdns/...>) And the point of renaming the package, actually Debian also ships it as package pdns and uses powerdns for directory names. The upstream RPM packages also place the files into /etc/powerdns and the package and tarball is named pdns. So we're consistent here.
