From: Greg Troxel <gdt@ir.bbn.com>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: Guile 2.x and `pkg-config'
Date: Sun, 09 Aug 2009 17:41:36 -0400 [thread overview]
Message-ID: <rmi7hxc64xb.fsf@fnord.ir.bbn.com> (raw)
In-Reply-To: <873a80spl8.fsf@gnu.org> ("Ludovic Courtès"'s message of "Sun, 09 Aug 2009 22:24:19 +0200")
[-- Attachment #1: Type: text/plain, Size: 367 bytes --]
ludo@gnu.org (Ludovic Courtès) writes:
> A recent thread on `guile-user' [0] raises an important concern: what
> should we do with `guile-1.8.pc' when 2.x is out?
>
> How about shipping `guile-1.8.pc' for compatibility, along with
> `guile.pc' (which would then become the Right One), both with
> "Version: 2.0"?
>
> Thoughts?
That sounds reasonable.
[-- Attachment #2: Type: application/pgp-signature, Size: 193 bytes --]
next prev parent reply other threads:[~2009-08-09 21:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-09 20:24 Guile 2.x and `pkg-config' Ludovic Courtès
2009-08-09 21:41 ` Greg Troxel [this message]
2009-08-12 22:36 ` Andy Wingo
2009-08-13 22:02 ` Neil Jerram
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=rmi7hxc64xb.fsf@fnord.ir.bbn.com \
--to=gdt@ir.bbn.com \
--cc=guile-devel@gnu.org \
--cc=ludo@gnu.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).