On Sun, Jun 16, 2013 at 5:35 AM, Christopher Meng <cickumqt@xxxxxxxxx> wrote: > Hi, > > I'm packaging serf into Fedora. > > Here is the review request: > > https://bugzilla.redhat.com/show_bug.cgi?id=973904 > > However, the reviewer said that this package should follow how was > packaged in oter distros. > > Debian and OpenSUSE install headers to /usr/include/serf-1/*.h, but I > just packaged them to /usr/include/*.h > > Now I decide to install them to a new folder, should I keep updated > with Debian or OpenSUSE, and install them to /usr/include/serf-1/, or > to /usr/include/serf/? > > Thanks. > > > Yours sincerely, > Christopher Meng serf is a relatively new library: I know that the next planned version of Subversion, version 1.8, plans to use it instead of the older "neon" librar, and they're excited aobut its performance benefits, so it behooves us to to make sure it's available. Putting it in "/usr/include/serf" or something like it would have made a lot more sense if the *upstream* authors had done so. They didn't, and that means that every application probing for it is going to have to have autoconf detect a new, non-author-specified include file location. That said, it's not unreasonable to be consistent with other RPM based distributions.. It is going to break *every single RPM* that does not have its autoconf or other configuration tools configured to add -I/usr/include/serf-1. -- packaging mailing list packaging@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/packaging
