From: Eli Zaretskii <eliz@gnu.org>
To: David Pirotte <david@altosw.be>
Cc: guile-devel@gnu.org
Subject: Re: guile-lib - devel branch - patch 4 of 11
Date: Wed, 20 Jul 2016 17:50:12 +0300 [thread overview]
Message-ID: <83twfkz7mj.fsf@gnu.org> (raw)
In-Reply-To: <20160719205344.255d1f88@capac> (message from David Pirotte on Tue, 19 Jul 2016 20:53:44 -0300)
> Date: Tue, 19 Jul 2016 20:53:44 -0300
> From: David Pirotte <david@altosw.be>
> Cc: guile-devel@gnu.org
>
> > > > > 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?
>
> > That's what I asked. Do you know the answer?
>
> Don't you understand? How could I possibly answer that quiz, since it's been 4 years
> I use 2.69? You can't tell for sure just because there has been no complain: you can
> only tell for sure if someone you 'trust' check with what ever version you'd like to
> use.
Problems in past versions of development tools are described in the
documentation, and if that's not enough, the maintainers of the tools
can be asked about them. There should be no need to learn about that
from personal experience alone.
> Besides, 'users' who locally manually install and compile GDB probably know a lot
> more then I on the subject :)
I don't think the fact that I build my own GDB means my time is cheap
and should be disregarded.
> And I bet they all setup a specific environment for that..
Not necessarily. E.g., I don't.
Once again, if we must use features that exist only in a newer
version, then it's a reason good enough to request users to upgrade.
But as long as no such features are required, doing this:
AC_PREREQ(2.69)
even though an older version would do, is IMO not a good idea.
And if you still disagree, let's leave it at that. I'm not speaking
for the Guile project, so my opinion can be easily overridden.
Thanks.
next prev parent reply other threads:[~2016-07-20 14:50 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
2016-07-18 2:40 ` Eli Zaretskii
2016-07-19 23:53 ` David Pirotte
2016-07-20 14:50 ` Eli Zaretskii [this message]
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=83twfkz7mj.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=david@altosw.be \
--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).