> Automake can't create all of the spec file. It doesn't have enough > information. And, adding the information to Makefile.am does not make > sense (because it is global to a package, which Makefile.am really > isn't). > > Also, generating a list of files is not enough. You also need pre- > and post- install and uninstall commands. > > One way to get these is the *_INSTALL variables, which I talked about > earlier. 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. --- Geoffrey Wossum [EMAIL PROTECTED]
- More an autopackage Geoffrey Wossum
- Re: More an autopackage Ganesan Rajagopal
- Re: More an autopackage David Lee
- Re: More an autopackage Alexandre Oliva
- Re: More an autopackage Rusty Ballinger
- Re: More an autopackage Geoffrey Wossum
- Re: More an autopackage Bob Friesenhahn
- Re: More an autopackage Tom Tromey
- Re: More an autopackage Tom Tromey
- Re: More an autopackage Geoffrey Wossum
- Re: More an autopackage Derek R. Price
- Re: More an autopackage Harlan Stenn
- Re: More an autopackage Tom Tromey
- Re: More an autopackage Derek R. Price
- RE: More an autopackage Bernard Dautrevaux
- Re: More an autopackage Geoffrey Wossum
- Re: More an autopackage Derek R. Price
- Re: More an autopackage Michael Sweet
- Re: More an autopackage Harlan Stenn
- Re: More an autopackage Pavel Roskin