Re: yaccvpath.test

[Tom Tromey]

Pavel> 1) "make dist" must ensure that out-of-date generated
Pavel> distributable files (parser.c, Makefile.in etc) are not
Pavel> included in the tarball either by running "make all" or
Pavel> otherwise. Yes or no?

Yes.  This has been on the to-do list for a long time.
I don't recall what has been holding it up.

Pavel> 2) "make distcheck" must ensure that out-of-date generated
Pavel> distributable files are not included in the tarball by exiting
Pavel> with non-zero code. Yes or no?

It would be nice but this is probably very hard, since the user can
add random targets to build just about anything.

Pavel> 3) Out-of-date generated distributable files should be
Pavel> recreated in the build directory. Always, never, only when no
Pavel> write permissions for srcdir?

There's not a general answer to this.

configure and Makefile.in, for example, must always be made in srcdir
regardless of any settings.

Other generated files might depend on the strictness setting.
(I don't know if any currently do.)

For yacc/lex output the answer probably depends on what the user wants
to happen.  For instance you might have one answer for the developer
and another answer after unpacking a `dist' tarball.

Pavel> 4) "make distclean" should attempt to clean generated
Pavel> distributable files that appear in the build directory. Yes or
Pavel> no?

Yes.  `make distclean' must leave the build directory as it was before
configure.  When `make distcheck' is failing in this test it is
because distclean is not properly doing its job -- in a fresh build
directory `configure ; make ; make distclean' must leave the directory
empty.

Tom