[Top][All Lists]

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

Re: Logical conflict between EXTRA_DIST and AC_OUTPUT

From: Stepan Kasal
Subject: Re: Logical conflict between EXTRA_DIST and AC_OUTPUT
Date: Mon, 18 Apr 2005 12:55:19 +0200
User-agent: Mutt/1.4.1i


On Sun, Apr 10, 2005 at 09:33:38PM +0100, Sergey Udaltsov wrote:
> In Makefile.am there is a line:
> EXTRA_DIST=... mypackage.spec
> At the same time I mention in configure.in AC_OUTPUT mypackage.spec -
> which is generated from mypackage.spec.in. Is is correct that "make
> distclean" removes the mypackage.spec (because it is in AC_OUTPUT).

If I understand it correctly, the only reason to keep mypackage.spec
in the tarball is that rpm can find it there and use it.
Thus I see no problem with the current behaviour.

The copy of mypackage.spec which was distributed is rewritten as soon
as you run ./configure.
The command "make distclean" means "remove all the files generated by the
./configure run".  Thusly, the "newly generated" mypackage.spec is removed.
(It makes no difference that it is identical to the original one.)

Have a nice day,
        Stepan Kasal

PS: If you really needed to change the behaviour so that distclean would
leave mypackage.spec there, you could achive it this way:

1) remove mypackage.spec from AC_OUTPUT
2) add the following to the top level Makefile.am:
EXTRA_DIST += mypackage.spec.in
$(srcdir)/mypackage.spec: ./config.status $(srcdir)/mypackage.spec.in
        $(SHELL) ./config.status --file=$@

reply via email to

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