Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v6 3/5] udev: convert to virtual package.
Date: Wed, 05 Feb 2014 13:52:55 +0100	[thread overview]
Message-ID: <87d2j1202g.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <CAAXf6LUbj5qTnNy7EHEsRhsNwaHk8yX8N=Ja9UFUM2EhOf=qNQ@mail.gmail.com> (Thomas De Schampheleire's message of "Wed, 5 Feb 2014 13:31:14 +0100")

>>>>> "Thomas" == Thomas De Schampheleire <patrickdepinguin@gmail.com> writes:

Hi,

 >> I find it odd that some packages depend on
 >> BR2_ROOTFS_DEVICE_CREATION_DYNAMIC_UDEV whereas others depend on
 >> BR2_PACKAGE_UDEV. To me, both symbols are interpreted as "the package needs a
 >> udev daemon to talk to at runtime" (whether via D-Bus or libudev). So I
 >> replaced both with BR2_PACKAGE_HAS_UDEV to be homogeneous. It is true that if
 >> a package depends on BR2_PACKAGE_HAS_UDEV, it is not explicitly said if it is
 >> a runtime or a build dependency. But, AFAIK, programs that want to communicate
 >> with the udev daemon do it via libudev/libgudev, so we end up with a build
 >> dependency.
 >> 
 >> In system/Config.in, I removed BR2_ROOTFS_DEVICE_CREATION_DYNAMIC_UDEV because
 >> I want the user to understand the change: he/she should not think of 'udev' as
 >> a package, but as a feature which, at this stage, is only available via eudev.
 >> I could have kept BR2_ROOTFS_DEVICE_CREATION_DYNAMIC_UDEV and have it select
 >> BR2_PACKAGE_EUDEV, but I've found it confusing.
 >> 
 >> But I should have added BR2_ROOTFS_DEVICE_CREATION_DYNAMIC_UDEV in
 >> Config.in.legacy to migrate to BR2_ROOTFS_DEVICE_CREATION_DYNAMIC_EUDEV.
 >> 
 >> In the end, the user selects BR2_ROOTFS_DEVICE_CREATION_DYNAMIC_EUDEV, which
 >> selects BR2_PACKAGE_EUDEV, which in turn selects BR2_PACKAGE_HAS_UDEV. All the
 >> packages depending on it are now available.

 > Based on your additional input, and rechecking the changes, I
 > understand your reasoning and accept it.
 > You still should add the legacy symbol, though.

 > Peter, what about you?

With the legacy handling added I'm fine with the rename.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2014-02-05 12:52 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-13 15:45 [Buildroot] [PATCH v6 0/5] udev is now provided by systemd or eudev Eric Le Bihan
2014-01-13 15:45 ` [Buildroot] [PATCH v6 1/5] sysvinit: depend on SysV selected as init system Eric Le Bihan
2014-01-13 22:35   ` Peter Korsgaard
2014-01-13 15:45 ` [Buildroot] [PATCH v6 2/5] eudev: new package Eric Le Bihan
2014-02-03 20:51   ` Thomas De Schampheleire
2014-01-13 15:45 ` [Buildroot] [PATCH v6 3/5] udev: convert to virtual package Eric Le Bihan
2014-02-03 21:41   ` Thomas De Schampheleire
2014-02-04 12:10     ` Eric Le Bihan
2014-02-05 12:31       ` Thomas De Schampheleire
2014-02-05 12:52         ` Peter Korsgaard [this message]
2014-02-04  8:47   ` Samuel Martin
2014-01-13 15:45 ` [Buildroot] [PATCH v6 4/5] systemd: bump to v207 Eric Le Bihan
2014-01-16 17:51   ` Samuel Martin
2014-01-17  8:36     ` Eric Le Bihan
2014-02-03 22:10   ` Thomas De Schampheleire
2014-02-04  8:41     ` Samuel Martin
2014-01-13 15:45 ` [Buildroot] [PATCH v6 5/5] manual: update /dev management section Eric Le Bihan
2014-02-03 22:14   ` Thomas De Schampheleire
2014-01-13 16:04 ` [Buildroot] [PATCH v6 0/5] udev is now provided by systemd or eudev Lucas De Marchi
2014-01-16 17:30   ` Lucas De Marchi
2014-01-16 20:44     ` Peter Korsgaard
2014-02-03 22:20 ` Thomas De Schampheleire

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=87d2j1202g.fsf@dell.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --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