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: Tue, 19 Jul 2016 20:53:44 -0300 [thread overview]
Message-ID: <20160719205344.255d1f88@capac> (raw)
In-Reply-To: <83y44z1xet.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1661 bytes --]
Hello,
> > > > 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.
I have no interest here, but if you do check and guarantee it works, I happy to
trust you.
> > > Besides, other packages might required older versions.
> > Are you aware of any incompatibilities between 2.69 and earlier 2.x version(s) of
> > autoconf?
> That's not the point.
It is exactly the point sorry. Besides, when a package requires an earlier version
then the latest stable, which is the case for Guile-Clutter for example, then
developers should provide a guidance for users, on how to exactly locally install
earlier then stable versions in a way that it does not interfere with the rest of
the system.
Besides, 'users' who locally manually install and compile GDB probably know a lot
more then I on the subject :) And I bet they all setup a specific environment for
that..
If they do not have a specific environment, these advanced 'users' [you mean top
notch hackers right?] know they can locally edit our configure.ac file and try what
ever version of autoconf they have... It will most probably work, I agree with you,
but I'm not interested to try and offer guarantee...
Cheers,
David
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-07-19 23:53 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 [this message]
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=20160719205344.255d1f88@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).