Hi. I'd like to speak a bit to what tthe right answer here is rather than what the policy currently says. It's sometimes fairly annoying to move a library out of the default path and to adjust the build system accordingly. Russ did that for one of krb5's private libraries, and in retrospect, I feel that the benefits don't justify the divergence from upstream. (It's not a huge patch, it just seems pointless and invasive to the build system)
I think that there are a number of things that should be sufficient to generally indicate a library is non-public: 1) move the library off the default search path 2) don't install a .so in a -dev package. I think in many cases 2 is sufficient and tends to involve less upstream changes. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
