The library package does not seem to be the correct place for device
nodes. People might install the lib for cross compilation and they will
not need the nodes. If a non-root user extracts the package
node-creation will fail.

On modern systems using debian packages the device nodes will be
generated by udev. And on legacy systems it should probably have been a
bunch of mknods in a post-install step instead of packaging the nodes.

Signed-off-by: Henning Schild <[email protected]>
---

I know 2.6 is discontinued and the debian subfolder is always a
controversial point, i still want to share that patch.

 debian/libxenomai1.dirs | 1 -
 debian/rules            | 1 -
 2 files changed, 2 deletions(-)

diff --git a/debian/libxenomai1.dirs b/debian/libxenomai1.dirs
index 8728b8b..35f4b51 100644
--- a/debian/libxenomai1.dirs
+++ b/debian/libxenomai1.dirs
@@ -1,4 +1,3 @@
 etc/modprobe.d
 etc/udev/rules.d
-dev/
 usr/share/lintian/overrides
diff --git a/debian/rules b/debian/rules
index 98b2531..fb485a8 100755
--- a/debian/rules
+++ b/debian/rules
@@ -61,7 +61,6 @@ install: build
        dh_prep
        dh_installdirs
        $(MAKE) install DESTDIR=$(CURDIR)/debian/tmp/
-       $(MAKE) devices DESTDIR=$(CURDIR)/debian/libxenomai1
        dh_install --sourcedir=$(CURDIR)/debian/tmp
        # xeno-config should be only in libxenomai-dev
        rm -f $(CURDIR)/debian/xenomai-runtime/usr/bin/xeno-config
-- 
2.7.3


_______________________________________________
Xenomai mailing list
[email protected]
https://xenomai.org/mailman/listinfo/xenomai

Reply via email to