[mojo-dev] [jira] (MRPM-87) Create SRPM

[Knut Vidar Siem (JIRA)]

Knut Vidar Siem edited a comment on MRPM-87 Create SRPM Consider the role of this plugin: it allows packaging of a number of pre-built files in an RPM package as part of a Maven build process. In other words, the "build" step (in RPM terms) is a no-op. This is also stated on the plugin's home page: [...] the spec files which are used do not do any build process (the plugin collects the files and "installs" them for packaging). Turning things around, like Rickard painfully describes, by inserting the Maven build at the RPM build step would be a very different overall build process and, although interesting in itself, not something that concerns this plugin. When using RPM as this plugin does, that is without a build step, constructing an SRPM should not in principle be harder than constructing the original RPM exactly because there is no building to be done. There is however the usage and validity of the SPEC file. To build an SRPM the SPEC file used to build the original RPM must be included and usable on a different system. It should be perfectly possible for this plugin to compile a SPEC file based on the plugin configuration that can be used as base for the construction of the original RPM and include it in an SRPM. This SPEC file must be usable with another RPM building tool than this plugin, e.g. rpmbuild. The construction of the source archive should be trivial. For my own use case I abandoned this plugin and did the above using Maven Assembly Plugin to create the source archive, Maven resource filtering to produce a SPEC file and invoked Ant's rpm task via Maven AntRun Plugin on the resulting SPEC file to build the RPM package. The end result was a tar.gz archive, a system-independent SPEC file that referenced this "source" archive and the RPM package built with the SPEC file. (We could have easily created an SRPM from the SPEC and the "source" archive but this was not a strict requirement.) It would be nice to do all this with this plugin and I don't see how allowing it would subvert the current role of the plugin. From my outside perspective, I see only one obstacle and that is that the SPEC file must be promoted from a by-product to an actual recipe for the RPM packaging – a good thing by itself in my opinion.

This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

--------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email