public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Laurent Guerby <guerby@acm.org>
To: Nathanael Nerode <neroden@twcny.rr.com>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: improving testing scheme (was Re: ACATS and GCC testsuite)
Date: Sat, 29 Mar 2003 12:25:00 -0000	[thread overview]
Message-ID: <1048927301.10770.182.camel@localhost.localdomain> (raw)
In-Reply-To: <20030328232500.GA1176@doctormoo>

On Sat, 2003-03-29 at 00:25, Nathanael Nerode wrote:
> Laurent Guerby said:
> >That's why I by far prefer to have the testing being done
> >after install, and not in build like it is done for GCC
> >via DejaGNU now. It looks like I have no chance
> >of changing this sad state of affair, but well I
> >can still make a separate package for Ada.
> 
> A lot of people mentioned the justification "You want to test it before 
> you install it, don't you?".

Well I'm probably stupid, but it makes no sense to me, what's magic
about installing? You install somewhere, put in PATH, play if it,
if it doesn't please you, you change your PATH, if you're short on space
you delete the install location. 100% reliable, safe and feel good
transaction semantics, and you're exactly in user situation with
no fragile hypothesis about release time.

> However, we would certainly like to make the in-build testing situation 
> a lot closer to the post-install testing situation by eliminating the 
> many curious flags which currently need to be passed to the tested 
> programs.  This is one of the motivations behind Per Bothner's "new 
> build scheme", which I'm still working on, albeit slowly.

Looks like overly complicated to my small brain, which
has just given up on the idea of doing anything with
the current in build Makefile mess and DejaGNU.

-- 
Laurent Guerby <guerby@acm.org>

  reply	other threads:[~2003-03-29  8:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-29  2:58 Nathanael Nerode
2003-03-29 12:25 ` Laurent Guerby [this message]
2003-04-02  7:49   ` Paul Jarc
2003-03-29 15:11 Richard Kenner
2003-03-29 15:51 Robert Dewar
2003-03-29 16:43 Richard Kenner
2003-04-01 23:53 ` Paul Jarc
2003-04-02  0:08 Richard Kenner
2003-04-02  0:26 ` Paul Jarc

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1048927301.10770.182.camel@localhost.localdomain \
    --to=guerby@acm.org \
    --cc=gcc@gcc.gnu.org \
    --cc=neroden@twcny.rr.com \
    /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).