Folks, Here's a policy question.
The libjpeg package, like many packages, uses a number of header files during compilation which are considered "internal," and only installs the "external" ones at install time. The external header files end up in the libjpeg package, but the internal ones don't. One of these internal files says: * These declarations are considered internal to the JPEG library; most * applications using the library shouldn't need to include this file. However, we now have another fink package in the submission tracker which needs that header at build time. That seems consistent with the statement "most applications shouldn't need to include this" -- a few might need it. (A comment in the code of the new package says: /* Although this file really should not have access to the library internals, * it is helpful to let it call jround_up () and jcopy_block_row (). */ #define JPEG_INTERNALS and this is what triggers the need for the internal headers.) The policy question is: should the new package download the libjpeg source and copy the needed headers into its build tree, or should the libjpeg package install the internal headers "by hand", for the benefit of this other package which wants them? -- Dave P.S. The INSTALL file in the new package seems to imply that Debian installs the internal headers in its jpeg-dev package. ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Fink-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fink-devel
