2017-01-31 00:37:24 +01:00
#
# Copyright (C) 2016 - 2017 Stijn Tintel <stijn@linux-ipv6.be>
#
# This is free software, licensed under the GNU General Public License v2.
# See /LICENSE for more information.
#
i n c l u d e $( TOPDIR ) / r u l e s . m k
PKG_NAME := domoticz
2018-06-15 17:50:03 +02:00
PKG_VERSION_MAJOR := 4
2019-09-27 00:35:14 +02:00
PKG_VERSION_PATCH := 10717
2018-06-15 17:50:03 +02:00
PKG_COMMIT :=
2017-01-31 00:37:24 +01:00
PKG_VERSION := $( PKG_VERSION_MAJOR) .$( PKG_VERSION_PATCH)
2019-12-25 01:51:09 +01:00
PKG_RELEASE := 3
2017-01-31 00:37:24 +01:00
domoticz: update to 3.9571 and clean up FHS handling
Upstream has merged a simplified version of the FHS patch, with a few
changes...
Scripts are actually configuration. There are examples, but the point is
that you write your own.
So they should live in the data directory (e.g. /var/lib/domoticz) not
in /usr/share/domoticz. The only exception is the dzVents runtime.
So.... the upstream patch handles the dzVents runtime bit. Drop the part
of our patch which added -scripts, because it can just be based in the
userdata directory and we don't need to change that.
Ship the default scripts/ directory in /etc/domoticz/scripts, and on
startup make a *symlink* to it from /var/lib/domoticz/scripts.
Symlink from /etc/domoticz/scripts/dzVents{data,generated_scripts} to
temporary directories under /var/lib/domoticz/dzVents so that those
directories (which are written to by Domoticz) don't land on the root
file system. Anyone with a writeable file system who *wants* the data/
directory to be persistent, can change that. Just as they can change
the userdata config option to point to a real file system somewhere.
Also drop the renaming of the OpenZWave Config/ directory. It's purely
cosmetric so there's no need for us to carry that change. It can go
upstream first, if it really offends anyone.
Drop the patches which are now merged upstream, and turn off the newly
added USE_OPENSSL_STATIC. Add -noupdates to the command line.
Finally, gzip the static www files to save space. In the common case,
clients will use "Accept-Encodiong: gzip" and Domoticz will serve them
as-is. It can also decompress on the fly if it really has to, but now we
aren't asking it to *compress* on the fly, which is probably a losing
proposition on an OpenWRT box.
Signed-off-by: David Woodhouse <dwmw2@infradead.org>
2018-05-13 16:52:50 +02:00
i f e q ( $( PKG_COMMIT ) , )
2017-01-31 00:37:24 +01:00
PKG_SOURCE := $( PKG_NAME) -$( PKG_VERSION) .tar.gz
PKG_SOURCE_URL := https://github.com/domoticz/domoticz/archive/$( PKG_VERSION) /$( PKG_SOURCE)
domoticz: update to 3.9571 and clean up FHS handling
Upstream has merged a simplified version of the FHS patch, with a few
changes...
Scripts are actually configuration. There are examples, but the point is
that you write your own.
So they should live in the data directory (e.g. /var/lib/domoticz) not
in /usr/share/domoticz. The only exception is the dzVents runtime.
So.... the upstream patch handles the dzVents runtime bit. Drop the part
of our patch which added -scripts, because it can just be based in the
userdata directory and we don't need to change that.
Ship the default scripts/ directory in /etc/domoticz/scripts, and on
startup make a *symlink* to it from /var/lib/domoticz/scripts.
Symlink from /etc/domoticz/scripts/dzVents{data,generated_scripts} to
temporary directories under /var/lib/domoticz/dzVents so that those
directories (which are written to by Domoticz) don't land on the root
file system. Anyone with a writeable file system who *wants* the data/
directory to be persistent, can change that. Just as they can change
the userdata config option to point to a real file system somewhere.
Also drop the renaming of the OpenZWave Config/ directory. It's purely
cosmetric so there's no need for us to carry that change. It can go
upstream first, if it really offends anyone.
Drop the patches which are now merged upstream, and turn off the newly
added USE_OPENSSL_STATIC. Add -noupdates to the command line.
Finally, gzip the static www files to save space. In the common case,
clients will use "Accept-Encodiong: gzip" and Domoticz will serve them
as-is. It can also decompress on the fly if it really has to, but now we
aren't asking it to *compress* on the fly, which is probably a losing
proposition on an OpenWRT box.
Signed-off-by: David Woodhouse <dwmw2@infradead.org>
2018-05-13 16:52:50 +02:00
e l s e
PKG_SOURCE := $( PKG_NAME) -$( PKG_COMMIT) .tar.gz
PKG_SOURCE_URL := https://github.com/domoticz/domoticz/archive/$( PKG_COMMIT) /$( PKG_SOURCE)
PKG_BUILD_DIR := $( BUILD_DIR) /$( PKG_NAME) -$( PKG_COMMIT)
e n d i f
2019-09-27 00:35:14 +02:00
PKG_HASH := c053a2161942529f56b748945ec297dcd67f449e68029fc886893a528891ad86
2017-01-31 00:37:24 +01:00
PKG_LICENSE := GPL-3.0
PKG_LICENSE_FILES := License.txt
2018-06-15 17:50:03 +02:00
PKG_BUILD_DEPENDS := python3
2017-01-31 00:37:24 +01:00
PKG_BUILD_PARALLEL := 1
PKG_USE_MIPS16 := 0
CMAKE_INSTALL := 1
i n c l u d e $( INCLUDE_DIR ) / p a c k a g e . m k
i n c l u d e $( INCLUDE_DIR ) / c m a k e . m k
d e f i n e P a c k a g e / d o m o t i c z
SECTION:= utils
CATEGORY:= Utilities
TITLE:= Open Source Home Automation System
URL:= http://domoticz.com/
MAINTAINER:= Stijn Tintel <stijn@linux-ipv6.be>
USERID:= domoticz = 6144:domoticz= 6144
DEPENDS:= \
+boost \
+boost-date_time \
+boost-system \
+boost-thread \
+libcurl \
+libmosquittopp \
+libopenssl \
+libopenzwave \
+libsqlite3 \
+libstdcpp \
2019-11-19 00:17:26 +01:00
+telldus-core \
2017-01-31 00:37:24 +01:00
+zlib
e n d e f
d e f i n e P a c k a g e / d o m o t i c z / d e s c r i p t i o n
Domoticz is a Home Automation System that lets you monitor and configure various devices like: Lights, Switches, various sensors/meters like Temperature, Rain, Wind, UV, Electra, Gas, Water and much more. Notifications/Alerts can be sent to any mobile device.
e n d e f
CMAKE_OPTIONS += \
2019-06-05 09:54:54 +02:00
-DBUILD_SHARED_LIBS= yes \
2019-05-09 06:34:22 +02:00
-DBoost_NO_BOOST_CMAKE= yes \
2017-01-31 00:37:24 +01:00
-DCMAKE_BUILD_TYPE= Release \
-DUSE_BUILTIN_MQTT= no \
-DUSE_BUILTIN_SQLITE= no \
-DUSE_STATIC_BOOST= no \
-DUSE_STATIC_LIBSTDCXX= no \
-DUSE_STATIC_OPENZWAVE= no \
domoticz: update to 3.9571 and clean up FHS handling
Upstream has merged a simplified version of the FHS patch, with a few
changes...
Scripts are actually configuration. There are examples, but the point is
that you write your own.
So they should live in the data directory (e.g. /var/lib/domoticz) not
in /usr/share/domoticz. The only exception is the dzVents runtime.
So.... the upstream patch handles the dzVents runtime bit. Drop the part
of our patch which added -scripts, because it can just be based in the
userdata directory and we don't need to change that.
Ship the default scripts/ directory in /etc/domoticz/scripts, and on
startup make a *symlink* to it from /var/lib/domoticz/scripts.
Symlink from /etc/domoticz/scripts/dzVents{data,generated_scripts} to
temporary directories under /var/lib/domoticz/dzVents so that those
directories (which are written to by Domoticz) don't land on the root
file system. Anyone with a writeable file system who *wants* the data/
directory to be persistent, can change that. Just as they can change
the userdata config option to point to a real file system somewhere.
Also drop the renaming of the OpenZWave Config/ directory. It's purely
cosmetric so there's no need for us to carry that change. It can go
upstream first, if it really offends anyone.
Drop the patches which are now merged upstream, and turn off the newly
added USE_OPENSSL_STATIC. Add -noupdates to the command line.
Finally, gzip the static www files to save space. In the common case,
clients will use "Accept-Encodiong: gzip" and Domoticz will serve them
as-is. It can also decompress on the fly if it really has to, but now we
aren't asking it to *compress* on the fly, which is probably a losing
proposition on an OpenWRT box.
Signed-off-by: David Woodhouse <dwmw2@infradead.org>
2018-05-13 16:52:50 +02:00
-DUSE_OPENSSL_STATIC= no \
2018-06-15 17:50:03 +02:00
-DUSE_PYTHON= yes \
domoticz: update to 3.9571 and clean up FHS handling
Upstream has merged a simplified version of the FHS patch, with a few
changes...
Scripts are actually configuration. There are examples, but the point is
that you write your own.
So they should live in the data directory (e.g. /var/lib/domoticz) not
in /usr/share/domoticz. The only exception is the dzVents runtime.
So.... the upstream patch handles the dzVents runtime bit. Drop the part
of our patch which added -scripts, because it can just be based in the
userdata directory and we don't need to change that.
Ship the default scripts/ directory in /etc/domoticz/scripts, and on
startup make a *symlink* to it from /var/lib/domoticz/scripts.
Symlink from /etc/domoticz/scripts/dzVents{data,generated_scripts} to
temporary directories under /var/lib/domoticz/dzVents so that those
directories (which are written to by Domoticz) don't land on the root
file system. Anyone with a writeable file system who *wants* the data/
directory to be persistent, can change that. Just as they can change
the userdata config option to point to a real file system somewhere.
Also drop the renaming of the OpenZWave Config/ directory. It's purely
cosmetric so there's no need for us to carry that change. It can go
upstream first, if it really offends anyone.
Drop the patches which are now merged upstream, and turn off the newly
added USE_OPENSSL_STATIC. Add -noupdates to the command line.
Finally, gzip the static www files to save space. In the common case,
clients will use "Accept-Encodiong: gzip" and Domoticz will serve them
as-is. It can also decompress on the fly if it really has to, but now we
aren't asking it to *compress* on the fly, which is probably a losing
proposition on an OpenWRT box.
Signed-off-by: David Woodhouse <dwmw2@infradead.org>
2018-05-13 16:52:50 +02:00
-DWITH_LIBUSB= no
2017-01-31 00:37:24 +01:00
2018-05-22 14:41:34 +02:00
TARGET_CFLAGS += -flto
TARGET_CXXFLAGS += -DWITH_GPIO -flto
2017-09-20 23:50:33 +02:00
2017-01-31 00:37:24 +01:00
d e f i n e B u i l d / P r e p a r e
$( call Build/Prepare/Default)
domoticz: update to 3.9571 and clean up FHS handling
Upstream has merged a simplified version of the FHS patch, with a few
changes...
Scripts are actually configuration. There are examples, but the point is
that you write your own.
So they should live in the data directory (e.g. /var/lib/domoticz) not
in /usr/share/domoticz. The only exception is the dzVents runtime.
So.... the upstream patch handles the dzVents runtime bit. Drop the part
of our patch which added -scripts, because it can just be based in the
userdata directory and we don't need to change that.
Ship the default scripts/ directory in /etc/domoticz/scripts, and on
startup make a *symlink* to it from /var/lib/domoticz/scripts.
Symlink from /etc/domoticz/scripts/dzVents{data,generated_scripts} to
temporary directories under /var/lib/domoticz/dzVents so that those
directories (which are written to by Domoticz) don't land on the root
file system. Anyone with a writeable file system who *wants* the data/
directory to be persistent, can change that. Just as they can change
the userdata config option to point to a real file system somewhere.
Also drop the renaming of the OpenZWave Config/ directory. It's purely
cosmetric so there's no need for us to carry that change. It can go
upstream first, if it really offends anyone.
Drop the patches which are now merged upstream, and turn off the newly
added USE_OPENSSL_STATIC. Add -noupdates to the command line.
Finally, gzip the static www files to save space. In the common case,
clients will use "Accept-Encodiong: gzip" and Domoticz will serve them
as-is. It can also decompress on the fly if it really has to, but now we
aren't asking it to *compress* on the fly, which is probably a losing
proposition on an OpenWRT box.
Signed-off-by: David Woodhouse <dwmw2@infradead.org>
2018-05-13 16:52:50 +02:00
# Fix APPVERSION/APPDATE since we don't build from a git tree
2017-01-31 00:37:24 +01:00
sed -i 's/#define APPVERSION.*/#define APPVERSION $(PKG_VERSION_PATCH)/' \
$( PKG_BUILD_DIR) /appversion.default
domoticz: update to 3.9571 and clean up FHS handling
Upstream has merged a simplified version of the FHS patch, with a few
changes...
Scripts are actually configuration. There are examples, but the point is
that you write your own.
So they should live in the data directory (e.g. /var/lib/domoticz) not
in /usr/share/domoticz. The only exception is the dzVents runtime.
So.... the upstream patch handles the dzVents runtime bit. Drop the part
of our patch which added -scripts, because it can just be based in the
userdata directory and we don't need to change that.
Ship the default scripts/ directory in /etc/domoticz/scripts, and on
startup make a *symlink* to it from /var/lib/domoticz/scripts.
Symlink from /etc/domoticz/scripts/dzVents{data,generated_scripts} to
temporary directories under /var/lib/domoticz/dzVents so that those
directories (which are written to by Domoticz) don't land on the root
file system. Anyone with a writeable file system who *wants* the data/
directory to be persistent, can change that. Just as they can change
the userdata config option to point to a real file system somewhere.
Also drop the renaming of the OpenZWave Config/ directory. It's purely
cosmetric so there's no need for us to carry that change. It can go
upstream first, if it really offends anyone.
Drop the patches which are now merged upstream, and turn off the newly
added USE_OPENSSL_STATIC. Add -noupdates to the command line.
Finally, gzip the static www files to save space. In the common case,
clients will use "Accept-Encodiong: gzip" and Domoticz will serve them
as-is. It can also decompress on the fly if it really has to, but now we
aren't asking it to *compress* on the fly, which is probably a losing
proposition on an OpenWRT box.
Signed-off-by: David Woodhouse <dwmw2@infradead.org>
2018-05-13 16:52:50 +02:00
COMMITDATE = ` tar tvfz $( DL_DIR) /$( PKG_SOURCE) --full-time | sed 's/.* \(20..-..-.. ..:..:..\) domoticz-.*/\1/;q' ` ; \
COMMITTS = ` date --date= " $$ $$ {COMMITDATE} " +%s` ; \
sed -i " s/#define APPDATE.*/#define APPDATE $$ $$ {COMMITTS}/ " $( PKG_BUILD_DIR) /appversion.default
i f n e q ( $( PKG_COMMIT ) , )
sed -i " s/#define APPHASH.*/#define APPHASH \" $( shell echo $( PKG_COMMIT) | cut -c1-8) \"/ " $( PKG_BUILD_DIR) /appversion.default
e n d i f
2017-01-31 00:37:24 +01:00
# Remove unwanted scripts
cd $( PKG_BUILD_DIR) /scripts && rm -rf \
buienradar_rain_example.pl \
2017-07-31 18:18:18 +02:00
_domoticz_main* \
2017-01-31 00:37:24 +01:00
download_update.sh \
domoticz: update to 3.9571 and clean up FHS handling
Upstream has merged a simplified version of the FHS patch, with a few
changes...
Scripts are actually configuration. There are examples, but the point is
that you write your own.
So they should live in the data directory (e.g. /var/lib/domoticz) not
in /usr/share/domoticz. The only exception is the dzVents runtime.
So.... the upstream patch handles the dzVents runtime bit. Drop the part
of our patch which added -scripts, because it can just be based in the
userdata directory and we don't need to change that.
Ship the default scripts/ directory in /etc/domoticz/scripts, and on
startup make a *symlink* to it from /var/lib/domoticz/scripts.
Symlink from /etc/domoticz/scripts/dzVents{data,generated_scripts} to
temporary directories under /var/lib/domoticz/dzVents so that those
directories (which are written to by Domoticz) don't land on the root
file system. Anyone with a writeable file system who *wants* the data/
directory to be persistent, can change that. Just as they can change
the userdata config option to point to a real file system somewhere.
Also drop the renaming of the OpenZWave Config/ directory. It's purely
cosmetric so there's no need for us to carry that change. It can go
upstream first, if it really offends anyone.
Drop the patches which are now merged upstream, and turn off the newly
added USE_OPENSSL_STATIC. Add -noupdates to the command line.
Finally, gzip the static www files to save space. In the common case,
clients will use "Accept-Encodiong: gzip" and Domoticz will serve them
as-is. It can also decompress on the fly if it really has to, but now we
aren't asking it to *compress* on the fly, which is probably a losing
proposition on an OpenWRT box.
Signed-off-by: David Woodhouse <dwmw2@infradead.org>
2018-05-13 16:52:50 +02:00
dzVents/{ .gitignore,documentation,examples,generated_scripts,data} \
2017-07-31 18:18:18 +02:00
dzVents/runtime/{ integration-tests,misc/smoothing.xlsx,tests} \
2017-01-31 00:37:24 +01:00
logrotate/ \
2017-07-31 15:23:33 +02:00
lua_parsers/example* \
lua/*demo.lua \
2017-01-31 00:37:24 +01:00
python/ \
readme.txt \
restart_domoticz \
templates/All.Python \
domoticz: update to 3.9571 and clean up FHS handling
Upstream has merged a simplified version of the FHS patch, with a few
changes...
Scripts are actually configuration. There are examples, but the point is
that you write your own.
So they should live in the data directory (e.g. /var/lib/domoticz) not
in /usr/share/domoticz. The only exception is the dzVents runtime.
So.... the upstream patch handles the dzVents runtime bit. Drop the part
of our patch which added -scripts, because it can just be based in the
userdata directory and we don't need to change that.
Ship the default scripts/ directory in /etc/domoticz/scripts, and on
startup make a *symlink* to it from /var/lib/domoticz/scripts.
Symlink from /etc/domoticz/scripts/dzVents{data,generated_scripts} to
temporary directories under /var/lib/domoticz/dzVents so that those
directories (which are written to by Domoticz) don't land on the root
file system. Anyone with a writeable file system who *wants* the data/
directory to be persistent, can change that. Just as they can change
the userdata config option to point to a real file system somewhere.
Also drop the renaming of the OpenZWave Config/ directory. It's purely
cosmetric so there's no need for us to carry that change. It can go
upstream first, if it really offends anyone.
Drop the patches which are now merged upstream, and turn off the newly
added USE_OPENSSL_STATIC. Add -noupdates to the command line.
Finally, gzip the static www files to save space. In the common case,
clients will use "Accept-Encodiong: gzip" and Domoticz will serve them
as-is. It can also decompress on the fly if it really has to, but now we
aren't asking it to *compress* on the fly, which is probably a losing
proposition on an OpenWRT box.
Signed-off-by: David Woodhouse <dwmw2@infradead.org>
2018-05-13 16:52:50 +02:00
update_domoticz \
domoticz.conf
2017-07-31 15:23:33 +02:00
# Remove *.md
cd $( PKG_BUILD_DIR) && $( FIND) -name '*.md' -delete
2017-01-31 00:37:24 +01:00
e n d e f
d e f i n e P a c k a g e / d o m o t i c z / i n s t a l l
2018-06-15 17:50:03 +02:00
$( INSTALL_DIR) $( 1) /etc/config $( 1) /etc/hotplug.d/tty $( 1) /etc/init.d $( 1) /etc/domoticz/plugins
2017-01-31 00:37:24 +01:00
$( INSTALL_BIN) ./files/domoticz.hotplug $( 1) /etc/hotplug.d/tty/domoticz
$( INSTALL_BIN) ./files/domoticz.init $( 1) /etc/init.d/domoticz
$( INSTALL_CONF) ./files/domoticz.config $( 1) /etc/config/domoticz
$( INSTALL_DIR) $( 1) /usr/share/domoticz $( 1) /usr/bin
domoticz: update to 3.9571 and clean up FHS handling
Upstream has merged a simplified version of the FHS patch, with a few
changes...
Scripts are actually configuration. There are examples, but the point is
that you write your own.
So they should live in the data directory (e.g. /var/lib/domoticz) not
in /usr/share/domoticz. The only exception is the dzVents runtime.
So.... the upstream patch handles the dzVents runtime bit. Drop the part
of our patch which added -scripts, because it can just be based in the
userdata directory and we don't need to change that.
Ship the default scripts/ directory in /etc/domoticz/scripts, and on
startup make a *symlink* to it from /var/lib/domoticz/scripts.
Symlink from /etc/domoticz/scripts/dzVents{data,generated_scripts} to
temporary directories under /var/lib/domoticz/dzVents so that those
directories (which are written to by Domoticz) don't land on the root
file system. Anyone with a writeable file system who *wants* the data/
directory to be persistent, can change that. Just as they can change
the userdata config option to point to a real file system somewhere.
Also drop the renaming of the OpenZWave Config/ directory. It's purely
cosmetric so there's no need for us to carry that change. It can go
upstream first, if it really offends anyone.
Drop the patches which are now merged upstream, and turn off the newly
added USE_OPENSSL_STATIC. Add -noupdates to the command line.
Finally, gzip the static www files to save space. In the common case,
clients will use "Accept-Encodiong: gzip" and Domoticz will serve them
as-is. It can also decompress on the fly if it really has to, but now we
aren't asking it to *compress* on the fly, which is probably a losing
proposition on an OpenWRT box.
Signed-off-by: David Woodhouse <dwmw2@infradead.org>
2018-05-13 16:52:50 +02:00
$( CP) $( PKG_INSTALL_DIR) /usr/dzVents $( 1) /usr/share/domoticz/dzVents
$( CP) $( PKG_INSTALL_DIR) /usr/Config $( 1) /usr/share/domoticz/Config
$( CP) $( PKG_INSTALL_DIR) /usr/scripts $( 1) /etc/domoticz/scripts
ln -sf /var/lib/domoticz/dzVents/generated_scripts $( 1) /etc/domoticz/scripts/dzVents
ln -sf /var/lib/domoticz/dzVents/data $( 1) /etc/domoticz/scripts/dzVents
2017-01-31 00:37:24 +01:00
$( CP) $( PKG_INSTALL_DIR) /usr/www $( 1) /usr/share/domoticz/
$( INSTALL_BIN) $( PKG_INSTALL_DIR) /usr/domoticz $( 1) /usr/bin/domoticz
domoticz: update to 3.9571 and clean up FHS handling
Upstream has merged a simplified version of the FHS patch, with a few
changes...
Scripts are actually configuration. There are examples, but the point is
that you write your own.
So they should live in the data directory (e.g. /var/lib/domoticz) not
in /usr/share/domoticz. The only exception is the dzVents runtime.
So.... the upstream patch handles the dzVents runtime bit. Drop the part
of our patch which added -scripts, because it can just be based in the
userdata directory and we don't need to change that.
Ship the default scripts/ directory in /etc/domoticz/scripts, and on
startup make a *symlink* to it from /var/lib/domoticz/scripts.
Symlink from /etc/domoticz/scripts/dzVents{data,generated_scripts} to
temporary directories under /var/lib/domoticz/dzVents so that those
directories (which are written to by Domoticz) don't land on the root
file system. Anyone with a writeable file system who *wants* the data/
directory to be persistent, can change that. Just as they can change
the userdata config option to point to a real file system somewhere.
Also drop the renaming of the OpenZWave Config/ directory. It's purely
cosmetric so there's no need for us to carry that change. It can go
upstream first, if it really offends anyone.
Drop the patches which are now merged upstream, and turn off the newly
added USE_OPENSSL_STATIC. Add -noupdates to the command line.
Finally, gzip the static www files to save space. In the common case,
clients will use "Accept-Encodiong: gzip" and Domoticz will serve them
as-is. It can also decompress on the fly if it really has to, but now we
aren't asking it to *compress* on the fly, which is probably a losing
proposition on an OpenWRT box.
Signed-off-by: David Woodhouse <dwmw2@infradead.org>
2018-05-13 16:52:50 +02:00
# compress static web content
find $( 1) /usr/share/domoticz/www -name "*.css" -exec gzip -9 { } \;
find $( 1) /usr/share/domoticz/www -name "*.js" -exec gzip -9 { } \;
2018-06-15 17:50:03 +02:00
gzip -9 $( 1) /usr/share/domoticz/www/*.html
gzip -9 $( 1) /usr/share/domoticz/www/secpanel/*.html
find $( 1) /usr/share/domoticz/www/views -name "*.html" -exec sh -c 'grep -q "<\!--#embed" {} || gzip -9 {}' \;
2017-01-31 00:37:24 +01:00
e n d e f
d e f i n e P a c k a g e / d o m o t i c z / c o n f f i l e s
/ e t c / c o n f i g / d o m o t i c z
/ v a r / l i b / d o m o t i c z /
domoticz: update to 3.9571 and clean up FHS handling
Upstream has merged a simplified version of the FHS patch, with a few
changes...
Scripts are actually configuration. There are examples, but the point is
that you write your own.
So they should live in the data directory (e.g. /var/lib/domoticz) not
in /usr/share/domoticz. The only exception is the dzVents runtime.
So.... the upstream patch handles the dzVents runtime bit. Drop the part
of our patch which added -scripts, because it can just be based in the
userdata directory and we don't need to change that.
Ship the default scripts/ directory in /etc/domoticz/scripts, and on
startup make a *symlink* to it from /var/lib/domoticz/scripts.
Symlink from /etc/domoticz/scripts/dzVents{data,generated_scripts} to
temporary directories under /var/lib/domoticz/dzVents so that those
directories (which are written to by Domoticz) don't land on the root
file system. Anyone with a writeable file system who *wants* the data/
directory to be persistent, can change that. Just as they can change
the userdata config option to point to a real file system somewhere.
Also drop the renaming of the OpenZWave Config/ directory. It's purely
cosmetric so there's no need for us to carry that change. It can go
upstream first, if it really offends anyone.
Drop the patches which are now merged upstream, and turn off the newly
added USE_OPENSSL_STATIC. Add -noupdates to the command line.
Finally, gzip the static www files to save space. In the common case,
clients will use "Accept-Encodiong: gzip" and Domoticz will serve them
as-is. It can also decompress on the fly if it really has to, but now we
aren't asking it to *compress* on the fly, which is probably a losing
proposition on an OpenWRT box.
Signed-off-by: David Woodhouse <dwmw2@infradead.org>
2018-05-13 16:52:50 +02:00
/ e t c / d o m o t i c z /
2017-01-31 00:37:24 +01:00
e n d e f
$( eval $ ( call BuildPackage ,domoticz ) )
