On Mittwoch, 14. Oktober 2015 17:03:45 CEST, Gianfranco Costamagna wrote:
Hi,
You realized that these files aren't symlinks but libraries? So really
don't think this would be correct. One example:
So I guess you should create the library and symlink the so file?
(I mean, a library and a library-dev with the so symlinked)
dynamic shared libraries without soname are so painful
(unless they are kept private, and I don't remember the package right now)
I know what you mean: that will make it impossible to install different
versions of libpanda3d. But I have no clue at all what should be symlinked.
I still don't understand, even after looking at the package
sed 's/@DEB_HOST_MULTIARCH@/$(DEB_HOST_MULTIARCH)/g'
debian/libpanda3d$(P3DVER).links.in >
debian/panda3d$(P3DVER).links
why a libpanda3d*.links.in becomes a panda3d*.links?
Oops, that was an mistake while renaming panda3d1.9.0 to libpanda3d1.9.0 as
requested.
at the end the result is somewhat correct, but I presume there
are some packaging issues,
e.g. the libpanda3d1.9.0 package contains .so files, but they
are just links.
I will rebuild and check that.
cheers,
G.
Best regards
