"Alfred M. Szmidt" <[EMAIL PROTECTED]> writes: > Hi! I added inetutils to my daily build scripts, and from now on > there should be a daily snapshot available from: > > Very cool. Maybe a note in README-alpha would be useful about this.
Yes, I suggest: --- README-alpha 05 Apr 2007 12:51:00 +0200 1.10 +++ README-alpha 11 Apr 2007 15:44:16 +0200 @@ -33,3 +33,12 @@ You can track the CVS process through the <[email protected]> mailing list. This is a medium volume moderated list. + +Daily snapshots built from CVS are available from: + + http://daily.josefsson.org/inetutils/ + +Log outputs from building the daily snapshot on some systems are +available from: + + http://autobuild.josefsson.org/inetutils/ > I notice that 'inetutils' doesn't contain _any_ self tests, which > seems bad. Maybe we could start working on that... > > It is hard to do a self test of interactive utilities like talk, ftp, > ... It is doable using dejagnu and such, but painful since you also > need to test the daemons; and that might require root permissions. > But if someone sends tests, then we can always add them, tests for > functions in libinetutils would be most welcome. Sure. > Any objections to installing the patch? > > My only objection is that m4/ shouldn't be used for this macro, the > macro should be put in acinclude.m4 instead. acinclude.m4 is deprecated according to the Automake manual: ,---- | The contents of `acinclude.m4', if this file exists, are also | automatically included in `aclocal.m4'. We recommend against using | `acinclude.m4' in new packages (*note Local Macros::). | ... | The first possibility (the historical practice) is to list all your | macros in `acinclude.m4'. This file will be included in `aclocal.m4' | when you run `aclocal', and its macro(s) will henceforth be visible to | `autoconf'. However if it contains numerous macros, it will rapidly | become difficult to maintain, and it will be almost impossible to share | macros between packages. | | The second possibility, which we do recommend, is to write each macro | in its own file and gather all these files in a directory. This | directory is usually called `m4/'. To build `aclocal.m4', one should | therefore instruct `aclocal' to scan `m4/'. From the command line, | this is done with `aclocal -I m4'. The top-level `Makefile.am' should | also be updated to define | `---- I don't volunteer to move what's in acinclude.m4 today to m4/ right now, but it seems that putting files in m4/ is the recommended approach. If you are worried about collisions with gnulib's *.m4, those files can be placed elsewhere and a --m4-base parameter or some bootstrap.conf additions could be used. /Simon _______________________________________________ bug-inetutils mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-inetutils
