[Bug 1301116] Review Request: libcxl - Coherent accelerator interface

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1301116



--- Comment #19 from Dan Horák <dan at danny.cz> ---
(In reply to Michel Normand from comment #16)
> (In reply to Dan Horák from comment #15)
> > additional comments:
> > - please update release for each iteration, it hard to track the changes
> > made if it's kept the same and spec and srpms are overridden
> 
> I will do for next
> 
> > - you can drop also the "build" dir for man pages, it's a no-op at the end
> > mkdir -p build/man3
> > cp man3/*.3 build/man3
> 
> There are other files in  man3/ I do not want to package
> this is the reason why i did a copy before to install build/man3/
> 
> > - I would use only VERS_LIB=%{version} otherwise it appends also ".1.fc24"
> > which is not correct IMO
> 
> I will do
> 
> > - the libcxl.so symlink need to be created manually or the makefile be
> > updated to create it, then "%files" should have
> > %{_libdir}/libcxl.so.*
> > and "%files devel" then
> > %{_libdir}/libcxl.so
> 
> I am lost :( for me the symbolic link is created by ldconfig at install time
> from the soname information present in the shipped so file
> ===
> $ls -ltr /usr/lib64/libcxl.so*
> -rwxr-xr-x. 1 root root 69216 mars   3 16:59 /usr/lib64/libcxl.so.1.3
> lrwxrwxrwx. 1 root root    13 mars   3 17:00 /usr/lib64/libcxl.so.1 ->
> libcxl.so.1.3

there are usually 3 files for a library
- first the versioned real file - /usr/lib64/libcxl.so.1.3
- second the symlink with soname (can be created by ldconfig) -
/usr/lib64/libcxl.so.1
- and last the development symlink libfoo.so that is used by a linker when
linking an app with the foo library
The first 2 files go to the main package (via %{_libdir}/libfoo.so.*), the last
one to the devel subpackage (via %{_libdir}/libfoo.so).

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are always notified about changes to this product and component