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, 24 Jul 2016 21:05:20 -0300	[thread overview]
Message-ID: <20160724210520.2da514b9@capac> (raw)
In-Reply-To: <83twfkz7mj.fsf@gnu.org>

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

Hello Eli,

> > 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.

I totally disagree with your last sentence, as a consequence of both what I've been
teached and what my experience 'told' me. So, if you have a well isolated
environment using an earlier version of autoconf and automake 1.14, I'll trust you.

Besides, should I agree with you, but I don't, I still have absolutely no time and no
interest to read about a 5y doc and ask maintainers quiz about 5y old version of
these tools.

> > 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.

I never implied that, this is a very unfair statement: you are the one who ask me to
spend my time to read and talk to maintainers about a more then 4y tool and doc.

At the very most, all you have to do is to locally edit the guile-lib configure.ac
and change AC_PREREQ(2.69) to what ever version you use and 'pass':  that does take
any time.

>   AC_PREREQ(2.69)
> 
> even though an older version would do, is IMO not a good idea.

This has nothing to do with an 'idea', it's about what we can guarantee: as I said
above, it's not ok for me to 'just' read, and if you can test 'make distcheck' and
tells me it's ok, using an earlier version of autoconf and automake 1.14, I'll trust
you.

> 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.

I don't speak in the name of Guile either, I am contributor. Note that this 
is Guile-Lib, not Guile (not that it would change my position wrt this, but...).

Thanks,
David

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

  reply	other threads:[~2016-07-25  0:05 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
2016-07-25  0:05               ` David Pirotte [this message]
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=20160724210520.2da514b9@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).