Shawn, Ok a patch to JIRA or PR would be cool. I am pretty sure we can in-line the init script reference so that it ends up in the RPM and our scripts already support 'start, stop, restart, etc..' so it should be doable.
As for making the upgrade process easy via RPM that will take a bit of thought but let's just go one step at a time. Thanks Joe On Mon, Jun 29, 2015 at 5:07 PM, Shawn Wells <[email protected]> wrote: > > > On 6/29/15 4:25 PM, Sean Busbey wrote: >> >> On Mon, Jun 29, 2015 at 3:17 PM, Joe Witt<[email protected]> wrote: >> >>> >Sean, >>> > >>> >Do you mind updating the contributor guide to reflect a preference >>> >(but not at the exclusion of)? >>> > >>> > >> >> Sure. Of patches-on-jira over github-pr, or something else? >> >> >>> >Regarding the muti-module do you think that is superior to simply >>> >having activated profiles for now? I just want to avoid restructuring >>> >until we 'know' the need. >>> > >>> > >> >> I think it depends on what's involved in the RPM packaging. If it's just >> an >> init script in src/main/resources, then sure restructuring is premature. >> If >> there are instructions beyond "-Prpm", then I think it's worth it if only >> for discoverability. > > > An RPM can be built as-is. > > Formal RHEL/CentOS packaging requirements want services to have an init > script, so "service nifi {start stop}" would work. We can worry about that > later, after an RPM is made.
