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: Sat, 16 Jul 2016 17:34:02 -0300	[thread overview]
Message-ID: <20160716173402.014d9a12@capac> (raw)
In-Reply-To: <83wpkm5c1u.fsf@gnu.org>

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

Hi Eli,

	nice to see progress on MinGW, congrat!

> > * configure.ac: Adding a copyright; bumping prereq -> 2.69  

> Why is that a good idea?

Why not? 
2.69 is the latest stable, available since April 2012

>  Are there any features Guile needs that older versions don't support?

It is not a just question of feature, but about running the same version [or higher]
then the one used to check, distcheck... Why would we want to even try to support any
previous version but the latest stable here?

I don't.

Autotool chain related issue/bugs can be very tedious to track down and solve, and
requiring users to install the latest stable versions, guarantee they won't have any
surprise on that side, and saves us precious time, we have other things to do.

IMO, it is the right thing to do.

Cheers,
David

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

  reply	other threads:[~2016-07-16 20:34 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 [this message]
2016-07-17  2:36     ` Eli Zaretskii
2016-07-17 20:26       ` David Pirotte
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=20160716173402.014d9a12@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).