Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=489686 --- Comment #2 from Conrad Sanderson <conradsand@xxxxxxxx> 2009-03-11 13:11:40 EDT --- (In reply to comment #1) Thanks for the feedback -- I will address these issues. I have a further question & clarification with respect to point (c): > > c) Split the package into a run-time package and a *-devel package > The library code is entirely in C++ header files, however routines from LAPACK, BLAS and ATLAS are called. As such there is a convenience component in the form of a dummy run-time library (libarmadillo.so), which simply pulls in the LAPACK, BLAS and ATLAS libraries. The idea is that a user can simply link against libarmadillo.so, rather than individually linking against LAPACK etc. In other words, the user can do this: g++ -o my_prog my_prog.cpp -larmadillo instead of a longer: g++ -o my_prog my_prog.cpp -L/usr/lib/atlas -lblas -llapack -llapack_atlas Hence I am not sure whether splitting the package into run-time and -devel packages is the best way to go. Suggestions ? -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. _______________________________________________ Fedora-package-review mailing list Fedora-package-review@xxxxxxxxxx http://www.redhat.com/mailman/listinfo/fedora-package-review