[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Stable branch release manager for Guile
From: |
Rob Browning |
Subject: |
Re: Stable branch release manager for Guile |
Date: |
14 Mar 2001 21:00:52 -0600 |
User-agent: |
Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7 |
Mikael Djurfeldt <address@hidden> writes:
> Exactly. Except that we're probably used to starting the count at
> zero in the third digit. (We're actually used to omitting the third
> digit when it "is" zero, but maybe it would be more consistent to
> spell it out.)
That's what I'd probably choose, but it's certainly not a big deal
either way.
> Interesting. I think you should start a discussion about this on
> the guile-devel list. Hopefully we can arrive at a proposal for how
> to do versioning as a result of that discussion.
>
> A further complication is that many "Guile modules", such as
> libgoops5 or libguilegtk, for example, are compiled differently
> depending on which Guile they are compiled "against". So, the
> versioning of a Guile dynamic linkable library should also reflect
> the *libguile* version number!
But wouldn't the dynamic linking (via ldso) handle making sure that
the goops .so file loads the right libguile when it's guile-level
dynamic-linked?
(I fully admit that although so far I've managed to get things to work
with g-wrap and g-wrap generated .so modules, I still don't *fully*
understand the dlopen linking vs ldso linking issues wrt to
sub-dependencies and multiple platforms, but you gotta start
somewhere :>)
In any case, I agree that we should discuss this on guile-devel.
--
Rob Browning <address@hidden> PGP=E80E0D04F521A094 532B97F5D64E3930