unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: David Pirotte <david@altosw.be>
To: Eli Zaretskii <eliz@gnu.org>
Cc: guile-devel@gnu.org
Subject: Re: guile-lib - devel branch - patch 4 of 11
Date: Sun, 17 Jul 2016 17:26:35 -0300	[thread overview]
Message-ID: <20160717172635.40bcfe87@capac> (raw)
In-Reply-To: <83vb053s9r.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 907 bytes --]

Hello Eli,

> > 2.69 is the latest stable, available since April 2012

> If there are known problems with older versions that get in the way, I
> agree.  Are there?

Are there?

> Because people might have older versions installed, and it's a nuisance to have to
> upgrade unrelated tools in your development environment just because you need to
> build a newer version of Guile.

I would not qualify autoconf/automake of 'unrelated' but 'essential' tools, and
would never call 'nuisance' the fact that you ask a user to be in the 'conditions'
that guarantee a proper build. I can not guarantee this proper build with earlier
versions, I don't have time neither any wish to maintain older version of these
essential tools.

> Besides, other packages might required older versions.

Are you aware of any incompatibilities between 2.69 and earlier 2.x version(s) of
autoconf?

David.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

  reply	other threads:[~2016-07-17 20:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-16  1:43 guile-lib - devel branch - patch 4 of 11 David Pirotte
2016-07-16  6:31 ` Eli Zaretskii
2016-07-16 20:34   ` David Pirotte
2016-07-17  2:36     ` Eli Zaretskii
2016-07-17 20:26       ` David Pirotte [this message]
2016-07-18  2:40         ` Eli Zaretskii
2016-07-19 23:53           ` David Pirotte
2016-07-20 14:50             ` Eli Zaretskii
2016-07-25  0:05               ` David Pirotte
2016-07-23 21:01       ` Andy Wingo

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=20160717172635.40bcfe87@capac \
    --to=david@altosw.be \
    --cc=eliz@gnu.org \
    --cc=guile-devel@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).