From: Rob Browning <rlb@defaultvalue.org>
Subject: Re: Policies about shared libs (directly affects .deb packaging)
Date: Wed, 13 Nov 2002 12:51:34 -0600 [thread overview]
Message-ID: <874raltia1.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <87isz1uz4j.fsf@raven.i.defaultvalue.org> (Rob Browning's message of "Wed, 13 Nov 2002 12:02:20 -0600")
Rob Browning <rlb@defaultvalue.org> writes:
> OK. Don't waste any more brainpower on this for now. I think I'm
> going to package the libs separately. If that doesn't work out, then
> we can continue the discussion.
OK. I've decided to break out libqthreads and libguile-ltdl since
they're fairly independent libs with no link against libguile, and
I've left the rest of the libs in guile-1.6-libs.
We'll see how that goes. We will still have the restriction that we
cannot change the major number of any of the libguile linked libs
during a stable series, and that we *must* change all the major
numbers of the libguile linked libs during a new release, but for the
most part, that just enforces good behavior.
--
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
prev parent reply other threads:[~2002-11-13 18:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-12 20:43 Policies about shared libs (directly affects .deb packaging) Rob Browning
2002-11-12 22:30 ` Neil Jerram
2002-11-12 23:13 ` Rob Browning
2002-11-13 18:02 ` Rob Browning
2002-11-13 18:51 ` Rob Browning [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874raltia1.fsf@raven.i.defaultvalue.org \
--to=rlb@defaultvalue.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).