[maemo-developers] packages: soname (0c2a, etc)

2006-07-26 Thread Murray Cumming
When creating maemo packages, we will tend to take the debian or Ubuntu
package and modify it for maemo. However, for C++ libraries, maybe the
soname would not be appropriate. Is there a policy for this, or can
someone suggest one?


The soname is the package suffix, such as 0c2a seen here:
http://packages.debian.org/unstable/libs/libsigc++-2.0-0c2a

I believe that these suffixes are changed whenever either
- A new version of g++, with a new C++ ABI, is used.
or
- A new version of libstdc++, with a new ABI, is used.

I don't know what the 0, c, 2, or a parts of the suffix mean, or if suffix
is just changed arbitrarily. I can't find an overview of these in the
debian documentation.

Maybe we could use the appropriate debian sonames, but we probably don't
have the same combinations of C++ and libstdc++ ABIs so there might be no
appropriate choice.


I could remove the soname/suffix from the package name, which would
involve a few more changes to the debian/ stuff than I'd like to make, so
I thought I'd check first.


Murray Cumming
[EMAIL PROTECTED]
www.murrayc.com
www.openismus.com

___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers


Re: [maemo-developers] packages: soname (0c2a, etc)

2006-07-26 Thread Murray Cumming
[snip]
 I could remove the soname/suffix from the package name, which would
 involve a few more changes to the debian/ stuff than I'd like to make,
 so
 I thought I'd check first.

 Bad idea :-) Those sonames are in debian to indicate that the abi has
 changed, and thus the packages depending on that lib needs to be
 recompiled.

But there is no previous version of the package for maemo.

Murray Cumming
[EMAIL PROTECTED]
www.murrayc.com
www.openismus.com

___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers


Re: [maemo-developers] packages: soname (0c2a, etc)

2006-07-26 Thread Adrian Neumaier
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Murray Cumming schrieb:
 [snip]
 I could remove the soname/suffix from the package name, which would
 involve a few more changes to the debian/ stuff than I'd like to make,
 so
 I thought I'd check first.
 Bad idea :-) Those sonames are in debian to indicate that the abi has
 changed, and thus the packages depending on that lib needs to be
 recompiled.
 
 But there is no previous version of the package for maemo.

Currently not, but who can foresee the future? :)
As maemo is just a debian derivate i'd just stick to the original. Makes
less problems usually.


Cheers
Adrian
- --
GPG Key ID: 42C33D97 | Reg. User #255628 (http://counter.li.org)
Fingerprint: 239D 7006 3CF0 8951 9FDA CA63 EF5C C95A 42C3 3D97
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.3 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQIVAwUBRMcn92cvsWk2zYzGAQpXIg//UB5RE7kpfxHrMQAWqTL29Xk2CMIX85Ms
fO0Ly9PTgJX3RrsX+guJDFZKWd9EsxgfNnwlIZvhpE7D5/0S34k0t2tXGiDpZ6YJ
1ZxiUjmAZ7AyxZStaFrT/ukSedLZwv72QkcWKjw/6HpgKUbUwAEghjp9ZKEnzwSF
pXEAT6JHchtIQ5CdM/0gc5m2QK9gbVSWukDCw+gPTkaHDweBVrnPFFFexvC1hyKz
MziAuzFH6YPRbQLxqzDYFiu5t2nqgeL22OgSMC0WB5zAPgmOQXJ6FDGfJDD3+9Rq
p3HjZ1vXCrq/yRn2dx0cRPcCtaPrFACYCISGs4wwGHdfY0MT+ZOM/R4TQ1oEh6Cs
y6W9Aq4wjL7lKmhw/9P06VSuoR3OIOGjo6Q4P2s1/p2H3zEVnY2vjhF7bIsWop/5
/ovhX7gXjbaRRVBZRZl3YKD7c97xSvUe0g2/A5eYk+vIWkldpHh9nOFcYuZB3Q8y
hNaUuAmZ1EtssnsZMCw5nfUxKPS9TkJRoqhvcue+mJXdatouog21AGr6k4dkBYiT
ivZPkbj1Uy5oY9AuwBokI49rU9mrPBjpX7HTXkqUYlT495lFquiAWG8Ls0YRGf3F
IvUsFQ+anovElSj8KC+YgF/Fk69hbG0sJ+V3c/qDWUrXF7l8GLC+2WhCpwqzaMcF
jA8n6zp2cbE=
=QNu2
-END PGP SIGNATURE-
___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers


Re: [maemo-developers] packages: soname (0c2a, etc)

2006-07-26 Thread Murray Cumming

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA512

 Murray Cumming schrieb:
 [snip]
 I could remove the soname/suffix from the package name, which would
 involve a few more changes to the debian/ stuff than I'd like to make,
 so
 I thought I'd check first.
 Bad idea :-) Those sonames are in debian to indicate that the abi has
 changed, and thus the packages depending on that lib needs to be
 recompiled.

 But there is no previous version of the package for maemo.

 Currently not, but who can foresee the future? :)
 As maemo is just a debian derivate i'd just stick to the original. Makes
 less problems usually.

But then the question is What is the original? The latest debian one, or
the one with an ABI (combination of g++, glibc, and libstdc++) that's most
similar to maemo's current ABI.

Maybe if I could find a policy document for debian, we could create a
policy for maemo.

Murray Cumming
[EMAIL PROTECTED]
www.murrayc.com
www.openismus.com

___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers


Re: [maemo-developers] packages: soname (0c2a, etc)

2006-07-26 Thread Adrian Neumaier
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Murray Cumming schrieb:
 But then the question is What is the original? The latest debian one, or
 the one with an ABI (combination of g++, glibc, and libstdc++) that's most
 similar to maemo's current ABI.

I suspect it's either etch or unstable. Maybe the Nokia/Maemo people can
tell us more.

 Maybe if I could find a policy document for debian, we could create a
 policy for maemo.

http://www.debian.org/devel/ should contain all information needed.

Cheers
Adrian

- --
GPG Key ID: 42C33D97 | Reg. User #255628 (http://counter.li.org)
Fingerprint: 239D 7006 3CF0 8951 9FDA CA63 EF5C C95A 42C3 3D97
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.3 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQIVAwUBRMcpjGcvsWk2zYzGAQpTmQ/9EArJbqg9U1FHw4HGm5mbATwThovr1RkI
/XQgSgsXjdYRnhrvquNIW0OS4sdViq7OPgJYRSdQR/8CbNY2DrM0EFgJ+M4koxVF
e1awbKmp+VWv4Imi1ElILVOUHolDfdRklTtkDakbyD74kXzK1yz+1G4u2+rn7sE4
EwYVe5VP/DhESRQzrFqE71QF0Y265srL7+uNegF0qwXe1Ss1JeSKfFmi+MTmDBbz
yMQpCGDj4Dh5rDqmlatswAZTsgCQ6IBvXAcfeme4X8CsykVbK5Mz3omNN0m312CC
Sje73uLRcRyjcVDXDME+zFaMpqB8vjNNQt3rapT1pq4pWY3ZuVjgi88wehYbhzO5
zYCHXXJVcAglA3yoG9Vgf5ff9BRqD0RRLzrfbM1h9jeHjQvyGqKuZeKV+XNy0a42
OHvV/MeJ3XO3pqLpVemYIrKRdUORIk8lTJfp7g+syaXK2JNhb+eRfFs1SZSMXF8z
bljQEO5NsZiPfUIfMB7iaqt2H5Z2u27VJSozbfRfv/wcWO5ePPjVS03wbfCSSapU
s1OcMYfjzzMrWXixkIwoWScqbYnI41C+SHe58cREb3qWZopxMHzk+FhVjHcrBPPV
Fd4mxMeTC1DGR+FTyU2TrRKj7+0n0yIwUjg2QsZ5GRyQ0GwDvDpP/6M/tWnl/Tho
jHph/kSNIR8=
=XP6y
-END PGP SIGNATURE-
___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers