From: Marius Vollmer <marius.vollmer@uni-dortmund.de>
Cc: Mikael Djurfeldt <djurfeldt@nada.kth.se>
Subject: Re: Release now?
Date: 25 Feb 2003 14:34:44 +0100 [thread overview]
Message-ID: <lju1es7abv.fsf@burns.dt.e-technik.uni-dortmund.de> (raw)
In-Reply-To: <rmi65r9u7mc.fsf@fnord.ir.bbn.com>
Greg Troxel <gdt@ir.bbn.com> writes:
> I'm all for shorter intervals between releases, but it would be good
> to make sure that packages expecting 1.6 can work with 1.8 (modulo
> insisting on a specific version when it isn't necessary, which is easy
> to patch).
Yes, we definitely need to be able to have two versions of Guile
installed with the same prefix and have them be usable for running
programs. However, I don't think we need to make special arrangements
for being able to compile against two versions of Guile at the same
time. Having to use different prefices for the two versions seems
acceptable to me.
Would pkg-config address this issue? I.e. could one say `guile-config
--use-version 1.6 link` (or something similar) with the effect that
the right '-L' and '-R' options are spit out?
However, a more serious problem exists for external modules of Scheme
code that want to use a specific version of Guile. For this, I think
we should add versions to our module system.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2003-02-25 13:34 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-24 12:37 Release now? Mikael Djurfeldt
2003-02-24 13:08 ` Dale P. Smith
2003-02-24 13:21 ` Mikael Djurfeldt
2003-02-24 13:32 ` Greg Troxel
2003-02-25 13:34 ` Marius Vollmer [this message]
2003-02-25 16:08 ` Greg Troxel
2003-02-25 18:38 ` Rob Browning
2003-02-26 1:51 ` Greg Troxel
2003-02-26 2:27 ` Rob Browning
2003-02-27 14:25 ` Greg Troxel
2003-02-27 15:21 ` pkg-config support for guile Greg Troxel
2003-03-22 23:31 ` Marius Vollmer
2003-04-23 21:22 ` Greg Troxel
2003-05-16 23:21 ` Marius Vollmer
2003-02-27 16:54 ` Release now? Rob Browning
2003-02-27 18:07 ` Greg Troxel
2003-02-27 18:45 ` Rob Browning
2003-02-27 19:25 ` Greg Troxel
2003-02-27 20:14 ` Rob Browning
2003-02-27 19:06 ` Rob Browning
2003-02-27 19:13 ` Rob Browning
2003-02-27 19:36 ` Greg Troxel
2003-02-27 20:02 ` Rob Browning
2003-02-27 20:54 ` Greg Troxel
2003-02-27 21:07 ` Dale P. Smith
2003-02-27 21:30 ` Dale P. Smith
2003-02-27 21:47 ` Rob Browning
2003-04-25 19:26 ` Neil Jerram
2003-02-25 16:28 ` Andreas Rottmann
2003-02-24 18:35 ` Rob Browning
2003-02-25 13:20 ` Marius Vollmer
2003-03-03 14:06 ` Mikael Djurfeldt
2003-04-25 19:28 ` Neil Jerram
2003-04-25 22:59 ` Marius Vollmer
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=lju1es7abv.fsf@burns.dt.e-technik.uni-dortmund.de \
--to=marius.vollmer@uni-dortmund.de \
--cc=djurfeldt@nada.kth.se \
/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).