Re: More an autopackage

[Derek R. Price]

Tom Tromey wrote:

> Unfortunately, I don't think it is that easy.
>
> First, Makefile.am contents can be conditional on the particular
> configuration.  That is why you really want to deal with the
> post-configuration package (using `make') and not Makefile.am.
>
> Second, the more complex post-install scripts are generated by
> automake itself.  For instance, take a look at the hair required to
> install an info page.  It would be a pain for developers to have to
> insert this code by hand (if they even know it exists).

Good point, but the general design I pointed out should still hold.
Only the generated Makefile would be the source for the data needed for
spec file generation rather than the Makefile.am, whether that's passed
in or scanned.  The pre/post install hair should be scannable from the
Makefile as well, whether that's for a shared library or info.

The spec file source would want room for install hooks as well, still.
That way instructions for, say, taking a daemon down and up again could
be inserted before automake acquires a daemon target.

Derek

--
Derek Price                      CVS Solutions Architect ( http://CVSHome.org )
mailto:address@hidden     OpenAvenue ( http://OpenAvenue.com )
--
Teacher is not a leper.
Teacher is not a leper.
Teacher is not a leper...

          - Bart Simpson on chalkboard, _The Simpsons_