Re: More an autopackage

[Derek R. Price]

Geoffrey Wossum wrote:

> I was thinking about this, and I considered another possibility.  autopkg
> would scan the Makefile.am to build a basic specfile, which the developer
> could then add pre/post install scripts and so forth.  This would be
> analogous to autoscan producing a basic configure.in that the developer
> then customizes.

You're probably better off having the scan tool create the spec file
dynamically from the Makefile.am & a source file analogous to acinclude.m4
or acconfig.h (look them up in the automake & autoconf docs, respectively).
That way when install targets get added to the Makefile.am the developer
won't have to copy them by hand into the final spec file.

Then your other piece would be a back end Bourne shell script which turned
the generated spec file & the sources into files and commands which it feeds
to the local package tool.  Maybe this task could be performed by the _Easy
Package Manager_ tool Ganesan Rajagopal pointed out?  I didn't look, but if
EMP isn't written in Bourne shell, it will probably have to be rewritten and
distributed like depcomp is.

Derek

--
Derek Price                      CVS Solutions Architect ( http://CVSHome.org )
mailto:address@hidden     OpenAvenue ( http://OpenAvenue.com )
--
Do not bite at the bait of pleasure till you know there is no hook.

                        - Thomas Jefferson