On Sun, 16 Jun 2013 17:35:44 +0800, Christopher Meng wrote: That's somewhat unusual. While we've got naming guidelines, which sometimes make it plausible to use package names that are used by other dists already, spending time on examining other dists' packages on where they store header files is beyond the scope of packaging for Fedora. So, where does upstream install those headers? You use the default location so far, since you don't modify the configure script's --includedir parameter: http://cicku.me/libserf.spec This depends on where dependencies expect these headers to be found. Do they evaluate the serf-1.pc pkgconfig --cflags to retrieve a custom search path for headers? Do external sources include the headers via standard search path, i.e. #include <serf.h> or #include <serf-1/serf.h> ? Do they use a hardcoded /usr/include/serf-1 search path? What is the full story here? Hint: it can be very helpful to use _less_ wildcards for important files like this one. If the filename changes, the automated RPM pkgconfig deps would change and break dependencies without warning you. Better spell out the full name of this file, because that would make the build fail and serve as an early-warning-system. (a similar thing may apply to other important file types, e.g. libs) It's part of the minimum build environment and doesn't need to be specified in the spec file. Here you should append %{?_isa} just like for the base package Requires. But are all these really required? $ grep \#include serf* serf_bucket_types.h:#include <apr_mmap.h> serf_bucket_types.h:#include <apr_hash.h> serf_bucket_types.h:#include "serf.h" serf_bucket_util.h:#include "serf.h" serf.h:#include <apr.h> serf.h:#include <apr_errno.h> serf.h:#include <apr_allocator.h> serf.h:#include <apr_pools.h> serf.h:#include <apr_network_io.h> serf.h:#include <apr_time.h> serf.h:#include <apr_poll.h> serf.h:#include <apr_uri.h> serf.h:#include "serf_bucket_types.h" -- Michael Schwendt Fedora release 19 (Schrödinger’s Cat) - Linux 3.9.5-301.fc19.x86_64 loadavg: 0.32 0.32 0.26

OK. I'll adopt remi's solution. And some unneeded requires are removed.

On Sun, Jun 16, 2013 at 5:35 AM, Christopher Meng <cickumqt(a)gmail.com&gt; wrote: 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.