[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#797888: RFS: panda3d/1.9.0-1 [ITP] -- Panda3D free 3D engine SDK



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hi Joern

ping, if you are still interested, please answer and fix the above :)
(or ask about how to fix it)

otherwise I'll close the RFS and unassign myself :)

cheers,

G.
On Sun, 25 Oct 2015 13:55:33 +0100 =?iso-8859-1?Q?J=F6rn_Sch=F6nyan?=
<joern.schoenyan@web.de> wrote:
> 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
> 
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJWPMvxAAoJEPNPCXROn13ZjNIP/27FSIENWmhgki97HyemA/Kp
Jx/DY4OWK4JndTsi2w/iLgxDIzn4h+cOjZE/M9fpL3XC8BJ3TS5ZauqfJf13eoOP
ScGbF/ji0aBtpD57oCcL6kwOf1iuRY15QjEjv4lqSCaZYswJqfJfxrvYaYUa4kKP
3L7MbcFYXLyZChPqhEtJhOr+ewEYurptAzznUrFtIpt4+0nDrD+KjgQYa+QDeEkN
uh3g5ZS4VwkVHvK9QIreW5bKW92kmG5HDjeRKjoPlN1xi6qTxavL3hDm+jbNlPm/
0jCMwUQmFjMu7h1jJMPiCYI8BFCaj4EWdt7SgFg4AGUP7WTQ18MiAD5xaaZQBGH5
179WzuvbcssQ34q2k9tc/yx1bA8rC+qDdBwRcsrpyetVioE5lR/mf0m+LQeqkORM
LrZmebQ20WeNullTbSs1UHoLzpHf7OWBsGcQ0F5czkgjL6xMNhegLg1yD+r5aRFw
2VKplyVXP5ecg9jlKEeG/PbNPbju5eMPS9iXDGkycQ9oM0orv62Q0IM7bXilq7IK
xzGfyEhe3Z2tUXk+xhZu1k3k1ajTE1p63Hl3LuGXrIQvOdyc1qOHerWonFzEINCG
jY9TbswTYHmR37xXM5tSk+3JwzAIMW84iImWZYVXqpr5WoFJRqjB3JGmWPx/LRkV
cAUPdzkUbn9ZBiR39tHY
=UOFO
-----END PGP SIGNATURE-----


Reply to: