On Thu, Mar 19, 2009 at 10:16 AM, Tobia Conforto
tobia.confo...@gmail.com wrote:
A developer who wants to build against chicken 3 or 4 will install the right
-dev package, which forces removal of the other versions. But this is a
developer-only process and a developer is supposed to either be
On Wed, Mar 18, 2009 at 9:27 PM, Ivan Raikov ivan.g.rai...@gmail.com wrote:
Hi Felix,
This means that we cannot have a Debian package for Chicken 4,
because Debian insists on having a soname version, so that it can do
things like installing libchicken 3 and 4 alongside each other. How
felix winkelmann wrote:
I wonder what's the point of enforcing use of soname, if (for
example) header-files are usually not versioned. What if you want to
install a chicken.h 3 and 4 alongside each other?
I believe it's a matter of end user support.
A developer who wants to build against
On Thu, Mar 19, 2009 at 3:18 AM, felix winkelmann bunny...@gmail.com wrote:
On Wed, Mar 18, 2009 at 9:27 PM, Ivan Raikov ivan.g.rai...@gmail.com wrote:
This means that we cannot have a Debian package for Chicken 4,
because Debian insists on having a soname version, so that it can do
things
Hi!
I just removed the use of soname from the build in trunk. It broke
explicit dynamic loading of core libraries. I just mention this in case
you have installed chicken 4 in the same prefix as a still used
chicken 3, because installing chicken 4 will now overwrite the
old libraries.
cheers,
Hi Felix,
This means that we cannot have a Debian package for Chicken 4,
because Debian insists on having a soname version, so that it can do
things like installing libchicken 3 and 4 alongside each other. How
does soname break explicit dynamic loading of core libraries?
-Ivan
felix
