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
