Perhaps the tack to sail on this component is not "make rpm" but "make
package", where a number of files is converted to a ~.spec,
prototype/pkginfo, ~.cmpnt/~.pkg/~.prod, or whatever:
1) list of files (source -> target)
2) inittab mods
3) rc.d mods
4) copywrite (with shorthand for current GPL, MPL, etc)
5) meta info: html webtree, author email, bugreport email
6) meta: requires package, conflicts with package
>From this, the relevant portions can be used to create the packaging
files, from which a package can be built. This is more generic, but may
require something like "libtool", except "pkgtool".
Allan
Hans Ulrich Niedermann wrote:
>
> Hi all,
>
> sorry to be replying to my own message, but I don't want to take
> credit for other people's ideas.
>
> Hans Ulrich Niedermann <[EMAIL PROTECTED]> writes:
>
> > Michael Bletzinger <[EMAIL PROTECTED]> writes:
> >
> > > Is anyone working on creating rpm targets similar to "make dist". I was
> > > thinking that automake could for example generate the spec file from a
> > > template.
> >
> > I've implemented "make rpm" in my experimental automake-based
> > package called "xtestsuite". It was more intended for myself to
> > somehow get into the the automake/autoconf thing so the C/C++ sources
> > are not very interesting.
>
> Waking up, I just remembered the software which gave me the idea
> to try it: At least some older (1.9.something) Samba releases also
> contained a "make rpm" function. But as Samba is rather a big project,
> it seemed too complicated to me at that that time to learn about
> Makefiles in general, automake/autoconf in special and RPM packaging
> from it at the same time.
>
> Perhaps I should have a look at samba again now - I'd suspect their
> rpm target is slightly more sophisticated than mine :-) Yet I don't
> know why they seem to have abandoned it - they seemed to have done so
> in the 2.0.[123] releases, if I remember correctly.
>
> Cheers,
>
> Uli
