Shawn

This sounds cool.  Yes feel free to submit a PR to github or you can
attach a patch to our JIRA [1]

We do already have support for generation of an RPM during the build.
You simply add '-Prpm'.  You can see how this is done in the assembly
pom here [2]

Would be happy to work with you getting this to a helpful state.  I
agree with you 'yum install nifi' is an awesomely convenient hook.
Just want to make sure we keep this up to date.  I am guessing we'd
not provide a convenience binary of the RPM like we do with the
tar.gz/zip but that is ok as the convenience binary is of course
easily built from the source too given a particular target
environment.

[1] https://cwiki.apache.org/confluence/display/NIFI/Contributor+Guide
[2] 
https://git-wip-us.apache.org/repos/asf/incubator-nifi.git/?p=incubator-nifi.git;a=blob_plain;f=nifi/nifi-assembly/pom.xml;hb=refs/heads/develop

Thanks
Joe

On Mon, Jun 29, 2015 at 4:05 PM, Shawn Wells <[email protected]> wrote:
>
>
> On 6/29/15 3:52 PM, Sean Busbey wrote:
>>
>> If we added a set of modules for packaging options, I'd love that.
>>
>> Maybe nifi-assembly could become a multimodule with the existing tarball
>> as
>> one submodule and the rpm packaging as another?
>
>
> I'm still familiarizing myself with the code and various installation steps,
> but this shouldn't be anything more than different make targets. An init
> script needs to be created to wrap bin/nifi.sh (but that's trivial).
>
> I'm working off RHEL7 and plan to build RPMs for that unless anyone screams
> loudly.
>
> Once I have some working code and process documentation, would the best way
> to start be to open a PR @ https://github.com/apache/incubator-nifi/ ?
>
>> My big concern with EPEL would be keeping current as NiFi adds new
>> versions. But so long as a user of an EPEL publish RPM could upgrade to a
>> newer one released by the project I'd be +1.
>
>
> EPEL packages have the advantage of doing releases whenever the package
> maintainer(s) want :)
>
> Being able to "yum install nifi" has really positive user experience
> implications for the guys I'm working with. I'm not sure how upgrading would
> work yet, mostly because I've never done a nifi upgrade (I've only gotten my
> feet wet with 3 installs).
>
> I couldn't find upgrade docs in the User Guide [1] or the Admin guide. Can
> someone point me to any existing guides that cover in-place upgrades (if
> that's even possible)?
>
>
>
> [1] http://nifi.incubator.apache.org/docs/nifi-docs/html/user-guide.html
> [2]
> http://nifi.incubator.apache.org/docs/nifi-docs/html/administration-guide.html

Reply via email to