From: Dagg Stompler <daggs@gmx.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] tvheadend: add dependency on udev
Date: Fri, 5 Jan 2018 11:35:01 +0200 [thread overview]
Message-ID: <20180105093501.5793-1-daggs@gmx.com> (raw)
udev is needed in order to detect usb based DVB cards.
reference for none SystemD systems can be found at https://github.com/tvheadend/tvheadend/blob/master/debian/tvheadend.init
Signed-off-by: Dagg Stompler <daggs@gmx.com>
---
v1 -> v2:
- use BR2_PACKAGE_HAS_UDEV instead of ROOTFS_DEVICE_CREATION_DYNAMIC_EUDEV (Thomas)
- add BR2_PACKAGE_HAS_UDEV dependecy to comment
package/tvheadend/Config.in | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/package/tvheadend/Config.in b/package/tvheadend/Config.in
index 44a69a27ba..75bb7d0b62 100644
--- a/package/tvheadend/Config.in
+++ b/package/tvheadend/Config.in
@@ -1,6 +1,7 @@
-comment "tvheadend needs a toolchain w/ NPTL, headers >= 3.2, dynamic library"
+comment "tvheadend needs a toolchain w/ NPTL, headers >= 3.2, dynamic library, udev /dev management"
depends on !BR2_TOOLCHAIN_HAS_THREADS_NPTL || \
- !BR2_TOOLCHAIN_HEADERS_AT_LEAST_3_2 || BR2_STATIC_LIBS
+ !BR2_TOOLCHAIN_HEADERS_AT_LEAST_3_2 || BR2_STATIC_LIBS || \
+ !BR2_PACKAGE_HAS_UDEV
depends on BR2_TOOLCHAIN_HAS_SYNC_4
config BR2_PACKAGE_TVHEADEND
@@ -9,6 +10,7 @@ config BR2_PACKAGE_TVHEADEND
depends on BR2_TOOLCHAIN_HAS_THREADS_NPTL
depends on BR2_TOOLCHAIN_HEADERS_AT_LEAST_3_2
depends on BR2_TOOLCHAIN_HAS_SYNC_4
+ depends on BR2_PACKAGE_HAS_UDEV
select BR2_PACKAGE_DTV_SCAN_TABLES
select BR2_PACKAGE_LIBICONV if !BR2_ENABLE_LOCALE
select BR2_PACKAGE_OPENSSL
--
2.15.1
next reply other threads:[~2018-01-05 9:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-05 9:35 Dagg Stompler [this message]
2018-01-05 22:54 ` [Buildroot] [PATCH v2] tvheadend: add dependency on udev Yann E. MORIN
2018-01-06 13:31 ` daggs
2018-01-06 14:25 ` Thomas Petazzoni
2018-01-11 7:14 ` Bernd Kuhls
2018-01-13 16:02 ` daggs
2018-01-13 22:22 ` Bernd Kuhls
2018-01-19 12:45 ` daggs
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180105093501.5793-1-daggs@gmx.com \
--to=daggs@gmx.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.