From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 07/15 v6] package/mesa3d: depends on libudev, not udev
Date: Mon, 27 Oct 2014 22:15:02 +0100 [thread overview]
Message-ID: <20141027221502.787a23d7@free-electrons.com> (raw)
In-Reply-To: <337a1970f6cec5755ed0b7ed73f3e6b31b84c2ca.1414442699.git.yann.morin.1998@free.fr>
Dear Yann E. MORIN,
On Mon, 27 Oct 2014 13:46:15 -0700, Yann E. MORIN wrote:
> diff --git a/package/mesa3d/Config.in b/package/mesa3d/Config.in
> index 74ebbed..b55173d 100644
> --- a/package/mesa3d/Config.in
> +++ b/package/mesa3d/Config.in
> @@ -9,7 +9,7 @@ menuconfig BR2_PACKAGE_MESA3D
> select BR2_PACKAGE_XLIB_LIBXDAMAGE if BR2_PACKAGE_XORG7
> select BR2_PACKAGE_XLIB_LIBXFIXES if BR2_PACKAGE_XORG7
> select BR2_PACKAGE_LIBXCB if BR2_PACKAGE_XORG7
> - depends on BR2_PACKAGE_HAS_UDEV
> + depends on BR2_PACKAGE_HAS_LIBUDEV
I thought the main conclusion from the meeting was that 'select' should
be used instead of 'depends on' for libudev, no?
From the report at http://elinux.org/Buildroot:DeveloperDaysELCE2014:
"We would also like to change the depends on libudev into select
libudev.".
Am I missing something here?
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-10-27 21:15 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-27 20:46 [Buildroot] [PATCH 0/15 v6] Introduce libudev (branch yem/libudev2) Yann E. MORIN
2014-10-27 20:46 ` [Buildroot] [PATCH 01/15 v6] support/gen-manual-lists.py: rework generating the virtual package list Yann E. MORIN
2014-10-27 20:46 ` [Buildroot] [PATCH 02/15 v6] package/libudev: new virtual package Yann E. MORIN
2014-10-27 20:46 ` [Buildroot] [PATCH 03/15 v6] package/eudev: is a provider for libudev Yann E. MORIN
2014-10-27 20:46 ` [Buildroot] [PATCH 04/15 v6] package/systemd: " Yann E. MORIN
2014-10-27 20:46 ` [Buildroot] [PATCH 05/15 v6] package/eudev: bump to 1.10 Yann E. MORIN
2014-10-29 20:24 ` Bernd Kuhls
2014-10-30 18:28 ` Bernd Kuhls
2014-10-27 20:46 ` [Buildroot] [PATCH 06/15 v6] package/eudev: split udev/libudev Yann E. MORIN
2014-10-27 20:46 ` [Buildroot] [PATCH 07/15 v6] package/mesa3d: depends on libudev, not udev Yann E. MORIN
2014-10-27 21:15 ` Thomas Petazzoni [this message]
2014-12-19 18:47 ` Yann E. MORIN
2014-10-27 20:46 ` [Buildroot] [PATCH 08/15 v6] package/libcec: needs libudev, not a udev daemon Yann E. MORIN
2014-10-27 20:46 ` [Buildroot] [PATCH 09/15 v6] package/libdrm: can also use only libudev Yann E. MORIN
2014-10-27 20:46 ` [Buildroot] [PATCH 10/15 v6] package/xdriver_xf86-input-evdev: needs libudev, not a udev daemon Yann E. MORIN
2014-10-27 20:46 ` [Buildroot] [PATCH 11/15 v6] [RFC] package/libatasmart: " Yann E. MORIN
2014-10-27 20:46 ` [Buildroot] [PATCH 12/15 v6] [RFC] package/libinput: " Yann E. MORIN
2014-10-27 20:46 ` [Buildroot] [PATCH 13/15 v6] [RFC] package/libusb: " Yann E. MORIN
2014-10-27 20:46 ` [Buildroot] [PATCH 14/15 v6] [RFC] package/vlc: " Yann E. MORIN
2014-10-27 20:46 ` [Buildroot] [PATCH 15/15 v6] [RFC] package/weston: " Yann E. MORIN
2014-10-27 21:41 ` [Buildroot] [PATCH 0/15 v6] Introduce libudev (branch yem/libudev2) Bernd Kuhls
2014-10-28 21:21 ` Arnout Vandecappelle
2014-10-29 6:00 ` Bernd Kuhls
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=20141027221502.787a23d7@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox