Product: Fedora
https://bugzilla.redhat.com/show_bug.cgi?id=892625

--- Comment #10 from Daniel Pocock <dan...@pocock.com.au> ---

All issues except rpath appear quite trivial to fix (and I've just done them in
trunk)

For the rpath issue:

* The configure.ac is relatively standard, no real hacks like some other
projects
* I bootstrap the upstream releases on a Debian 6 (squeeze) system with the
Debian autotools, that generates the configure script
* according to the Debian wiki about rpath, there are slight differences in the
way libtool works in this scenario because Fedora has lib64 and Debian had
lib32
* I suspect that running autoreconf will generate another configure script that
is more Fedora friendly - is it safe to do that from within a spec file?  Have
you seen this done elsewhere?


http://wiki.debian.org/RpathIssue

Can you also comment on the %doc issue?  Should I just include it in one (or
all?) of the %files sections?  E.g.

%files libs
%doc COPYING
%{_libdir}/libb2bua-*.so
%{_libdir}/libdum-*.so
%{_libdir}/librepro-*.so
%{_libdir}/libresip-*.so
%{_libdir}/libreTurnClient-*.so
%{_libdir}/librutil-*.so
%{_libdir}/libsipdial-*.so

Or is there some way to tell it that file belongs in every package?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug 
https://bugzilla.redhat.com/token.cgi?t=R1UAv0QipJ&a=cc_unsubscribe
_______________________________________________
package-review mailing list
package-review@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/package-review

Reply via email to