Re: DejaGnu 1.4.4 release

Re: DejaGnu 1.4.4 release

[Michael Elizabeth Chastain]

Andrew asks the key questions:
> - should src/dejagnu/ be replaced?
> - should src/dejagnu/ be removed?

My opinion:

Go for removal first.  Tell people that the sourceware versions of
Expect and Dejagnu are going away and they need to use the upstream
versions.  Provide doco for downloading and building Tcl+Expect+Dejagnu.
(I can do that part).

Wait a month.  If no one objects, then kill the sourceware versions
of Expect and Dejagnu.

Michael C

Re: DejaGnu 1.4.4 release

[Michael Elizabeth Chastain]

> DejaGnu 1.4.4 has been released.

Works fine for me with the gdb test suite on native i686-pc-linux-gnu
(106 configurations) and native hppa2.0w-hp-hpux11.11 (1 configuration).

Michael C

DejaGnu 1.4.4 release

[Ben Elliston]

DejaGnu 1.4.4 has been released.

This release cleans up the source tree, makes a start at overhauling
the documentation, updates to modern versions of build tools like
automake and autoconf and applies patches that have been accumulating
in the sibling source repository at sources.redhat.com.

The hope is that these cleanups will make it easier to start improving
DejaGnu on a wider scale.  Feel free to submit suggestions to the
DejaGnu mailing list for improvements.

Major changes from 1.4.2 and 1.4.3:

    1. New XML output option, so test results can be loaded into a database.
    2. Support for the KFAIL/KPASS (known failures).
    3. New "Hello World" example.
    4. New tutorial chapter.
    5. Test cases build with either GCC 2.x or 3.x.
    6. BlueGnu has been removed from the contrib directory.
    7. The contrib/test* scipts were bitrotten and have been removed.  If
       you still want copies of these, they can be found in the previous
       DejaGnu release.
    8. i960glue.c has been removed.

The source tar file is now available from:

    ftp.gnu.org:/pub/gnu/dejagnu/dejagnu-1.4.4.tar.gz

The MD5 checksum of the file is:

    MD5 (dejagnu-1.4.4.tar.gz) = 053f18fd5d00873de365413cab17a666

Enjoy!

Re: DejaGnu 1.4.4 release

[Andrew Cagney]

[Ben, nice!] Now the questions:

- should src/dejagnu/ be replaced?
- should src/dejagnu/ be removed?

I don't personally care either way (but don't try to sign me up for any 
heavy lifting :-).

Andrew

> DejaGnu 1.4.4 has been released.
> 
> This release cleans up the source tree, makes a start at overhauling
> the documentation, updates to modern versions of build tools like
> automake and autoconf and applies patches that have been accumulating
> in the sibling source repository at sources.redhat.com.
> 
> The hope is that these cleanups will make it easier to start improving
> DejaGnu on a wider scale.  Feel free to submit suggestions to the
> DejaGnu mailing list for improvements.
> 
> Major changes from 1.4.2 and 1.4.3:
> 
>     1. New XML output option, so test results can be loaded into a database.
>     2. Support for the KFAIL/KPASS (known failures).
>     3. New "Hello World" example.
>     4. New tutorial chapter.
>     5. Test cases build with either GCC 2.x or 3.x.
>     6. BlueGnu has been removed from the contrib directory.
>     7. The contrib/test* scipts were bitrotten and have been removed.  If
>        you still want copies of these, they can be found in the previous
>        DejaGnu release.
>     8. i960glue.c has been removed.
> 
> The source tar file is now available from:
> 
>     ftp.gnu.org:/pub/gnu/dejagnu/dejagnu-1.4.4.tar.gz
> 
> The MD5 checksum of the file is:
> 
>     MD5 (dejagnu-1.4.4.tar.gz) = 053f18fd5d00873de365413cab17a666
> 
> Enjoy!
> 

Re: DejaGnu 1.4.4 release

[Ben Elliston]

Hi Andrew

> - should src/dejagnu/ be replaced?

IMHO, yes.  The 1.4.4 release is very close to the version in
src/dejagnu.  I've since merged a handful of patches from src -> FSF
that were missed and I've a patch that can be applied after a 1.4.4
import that will ensure that nothing will be lost from src/dejagnu.

> - should src/dejagnu/ be removed?

What would the alternative be?  To just expect (ha!) developers to
have DejaGnu installed on their systems?

I think as a first step, we should go with the former.  After a bit of
time, we can consider removing it from src altogether.

Cheers, Ben

Re: DejaGnu 1.4.4 release

[Gerald Pfeifer]

On Thu, 6 Feb 2004, Ben Elliston wrote:
>> - should src/dejagnu/ be replaced?
> IMHO, yes.  The 1.4.4 release is very close to the version in
> src/dejagnu.  I've since merged a handful of patches from src -> FSF
> that were missed and I've a patch that can be applied after a 1.4.4
> import that will ensure that nothing will be lost from src/dejagnu.

Thanks!

>> - should src/dejagnu/ be removed?
> What would the alternative be?  To just expect (ha!) developers to
> have DejaGnu installed on their systems?

Yes.  If not right away, than in the mid term: we require casual
testers of CVS GCC to have bison and developers to have autoconf
etc.; and if upstream DejaGnu "just works", let's use that.

Most distributions will provide DejaGnu as a package anyway.

Gerald
-- 
Gerald Pfeifer <gp@suse.de>    Technical Project Manager, SUSE Linux AG

Re: DejaGnu 1.4.4 release

[Joe Buck]

On Thu, Feb 05, 2004 at 09:47:28PM +0100, Gerald Pfeifer wrote:
> On Thu, 6 Feb 2004, Ben Elliston wrote:
> >> - should src/dejagnu/ be removed?
> > What would the alternative be?  To just expect (ha!) developers to
> > have DejaGnu installed on their systems?

The tester population is larger than the developer population.

> Yes.  If not right away, than in the mid term: we require casual
> testers of CVS GCC to have bison and developers to have autoconf
> etc.; and if upstream DejaGnu "just works", let's use that.
> 
> Most distributions will provide DejaGnu as a package anyway.

We should have a pointer on the web site to the DejaGnu source, for
testers on platforms that don't have it already packaged for them.