libcdio-paranoia includes are under cdio because these are cdio paranoia headers (as opposed to the original cd-paranoia or some other kind of paranoia.) I gather that's not at issue.
The paranoia directory I added to make it clear which headers belong to which package. libcdio-paranoia and libcdio have different licenses; in the past they were put together and that has caused consternation. Having these in separate directories, in my view made, this split clearer. Also makes it clear that you need libcdio in order to use libcdio-paranoia. On Fri, Nov 23, 2012 at 8:35 AM, Adrian Reber <[email protected]> wrote: > On Sat, Oct 27, 2012 at 07:21:29PM -0400, Rocky Bernstein wrote: > > On ftp.gnu.org are releases libcdio 0.90 and libcdio-paranoia10.2+0.90. > > Another question concerning libcdio-paranoia and its include files. > Using git commit b2807f3c7a > "Makefile.am: install headers in cdio/paranoia" > > the include files are (using a prefix of /usr) installed in > > /usr/include/cdio/paranoia/cdda.h > /usr/include/cdio/paranoia/paranoia.h > > Is this actually desired? All applications are searching for cdio/cdda.h > and cdio/paranoia.h. The code has to be changed to use paranoia/cdda.h > and paranoia/paranoia.h. I am not against changing the code of the > applications, I just want to know if this is actually desired? > > Adrian > >
