Yes, but probably not as a part of the Director module itself. We want to provide a generic mechanism for all Icinga Web 2 modules. That's basically pretty easy, as creating a SPEC or a debian/rules + .install file for a module is (given their unique structure) ridiculously easy.
It basically consists of "copy everything to /usr/share/icingaweb2/modules/<modulename>", that's it. Usually not a single line has to be modified, no configure/automake/whatever. Configuration is stored outside of the module tree, that way they never get polluted. And packages should neither enable nor configure modules anyways. We wanted to have this since a very long time, it's just a matter of priorities. Recently we rolled out a new build server, Icinga Exchange will get new features very soon, both have been dependencies for the "package all the modules" task. We are getting closer, but there is no scheduled date right now, sorry. It currently has low priority. However, in case you already have some basic experience with creating packages (or feel comfortable with googling such things) you should perfectly be able to create them on your own right now. Am 27.07.2016 um 12:35 schrieb Joosten, Markus:
Hello list, can anyone tell me if there is a plan to release the director module as a system package (rpm/deb)? Any hints are greatly appreciated. Regards, Markus
-- Thomas Gelf Principal Consultant NETWAYS GmbH | Deutschherrnstr. 15-19 | D-90429 Nuernberg Tel: +49 911 92885-0 | Fax: +49 911 92885-77 CEO: Julian Hein, Bernd Erk | AG Nuernberg HRB18461 http://www.netways.de | thomas.g...@netways.de ** OSBConf 2016 - September - osbconf.org ** ** OSMC 2016 - November - netways.de/osmc ** _______________________________________________ icinga-users mailing list icinga-users@lists.icinga.org https://lists.icinga.org/mailman/listinfo/icinga-users
