bug-gnulib
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug-gnulib] Re: gnulib repository


From: Jeff Bailey
Subject: [Bug-gnulib] Re: gnulib repository
Date: Mon, 22 Oct 2001 06:24:53 -0700
User-agent: Mutt/1.2.5i

I have added address@hidden to this cc: list.  All discussions
really ought to take place there.

On Fri, Oct 19, 2001 at 06:45:50PM +0100, Gary V. Vaughan wrote:

> > I think config.{guess,sub}
> > reside on savannah in a module called "config", but perhaps the
> > maintainer will agree to join them in.
> 
> Hi Ben!  What do you say... it would be great to have a single module
> for all this stuff, no?

I'm open to that if he's interested.

> > texinfo.tex may be part of the
> > texinfo package.
> 
> The master copy is currently maintained at ftp://ftp.gnu.org/gnu/GNUinfo/
> (presumably by the texinfo maintainers), so it seems like a good idea to
> move it to gnulib.

I'll email them today.

> If the up to date version of COPYING and COPYING.LIB are to go in, I
> think you should also keep ftp://ftp.gnu.org/gnu/GNUinfo/fdl.texi in
> gnulib, and maybe a plain text version too?

rms has confirmed that this is okay.  COPYING, COPYING.LIB,
COPYING.DOC, and fdl.texi are now sourced in our repository.

> > The others should definetly be in there.  Can you recommend a package
> > that would have a fairly recent and patched version?
> 
> I synchronise with glibc, but I am not sure that this is necessarily the
> master copy...

It's a good enough start, thanks.

> > In my ideal world, we will achieve high enough quality control on
> > gnulib that the build chain folks will join this effort.  Towards
> > that end, I plan to write a test suite to go along with gnulib, so
> > that maintainers can feel comfortable that functionality will
> > always be preserved and that there will be no regressions.

> Cool.  Please don;t use DejaGNU though, it requires too much other
> cruft to be useful... a bunch of shell scripts with generated
> automake check rules would be easier to maintain... or even
> Autoconf's new AutoTest sub package.

Well, I've been wanting to start using testsuites for a while now, and
haven't found an ideal one.  I'll take a look at AutoTest.

-- 
Abandon the search for truth; settle for a good fantasy.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]