From: Marius Vollmer <mvo@zagadka.ping.de>
Cc: guile-devel@gnu.org
Subject: Re: Tool version in HACKING
Date: 15 Apr 2002 15:59:13 +0200 [thread overview]
Message-ID: <87y9fpoyfi.fsf@zagadka.ping.de> (raw)
In-Reply-To: <200204091928.MAA18084@onyx.he.net>
Gary Houston <ghouston@arglist.com> writes:
> > on 2001-11-22, you have removed the required tool version numbers from
> > the HACKING file (see ChangeLog entry below). Why did you do this?
> >
> > I think they are an important bit of information since Guile will
> > indeed not work with all old versions.
> >
> > 2001-11-22 Gary Houston <ghouston@arglist.com>
> >
> > * HACKING: Modified the Hacking It Yourself section.
> > Removed the version numbers from the tools.
>
> The versions seemed a bit out of date, and the last policy I remember
> is that the latest released versions are always used.
Ahh, I see. I didn't know about the "latest released versions" rule.
> Since it's easy to find out what the versions are, it doesn't seem
> necessary to list them in the file and saves the confusion when the
> released versions differ from the file versions (is the file correct
> or did somebody just forget to update it?)
Yes, that makes sense to me. Since we can now request specific
automake and autoconf versions from Makefile.am and configure.in
directly, we should just do this. I.e., we now have AC_PREREQ(2.53)
in configure.in which will fail for autoconf versions less than 2.53.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
prev parent reply other threads:[~2002-04-15 13:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-09 17:12 Tool version in HACKING Marius Vollmer
2002-04-09 19:28 ` Gary Houston
2002-04-10 6:29 ` Thien-Thi Nguyen
2002-04-10 15:07 ` Rob Browning
2002-04-10 18:42 ` Thien-Thi Nguyen
2002-04-22 16:59 ` Thien-Thi Nguyen
[not found] ` <200204091928.MAA18084@onyx.he.net>
2002-04-15 13:59 ` Marius Vollmer [this message]
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=87y9fpoyfi.fsf@zagadka.ping.de \
--to=mvo@zagadka.ping.de \
--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).