Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Le Bihan <eric.le.bihan.dev@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v7 0/4] udev is now provided by systemd or eudev
Date: Mon, 10 Feb 2014 14:44:15 +0100	[thread overview]
Message-ID: <20140210134415.GD22843@pc-eric> (raw)
In-Reply-To: <52F5435A.3080700@mind.be>

Hi!

On Fri, Feb 07, 2014 at 09:34:34PM +0100, Arnout Vandecappelle wrote:
>
>  I have one more remark about the way the udev virtual package is
> implemented. We found out for the opengl packages that there is a better
> way to do it, something like:
>
> udev/Config.in:
>
> config BR2_PACKAGE_HAS_UDEV
>         bool
>
> config BR2_PACKAGE_PROVIDES_UDEV
>         depends on BR2_PACKAGE_HAS_UDEV
>         string
>
>
> udev/udev.mk:
>
> UDEV_SRC =
> UDEV_DEPENDENCIES = $(call qstrip,$(BR2_PACKAGE_PROVIDES_UDEV))
>
> ifeq ($(UDEV_DEPENDENCIES),)
> define UDEV_CONFIGURE_CMDS
>         echo "No Udev implementation selected. Configuration error."
>         exit 1
> endef
> endif
>
>
> eudev/Config.in:
>
> ...
> if BR2_PACKAGE_EUDEV
> config BR2_PACKAGE_PROVIDES_UDEV
> 	default "eudev"
> endif
>
>
>
>  That moves all the provider logic to the provider itself, which for
> instance makes it possible for BR2_EXTERNAL to provide an alternative
> udev implementation (e.g. a different udev version, which could be _very_
> relevant).
>
>
>  I repeat, though: this can be done as a follow-up patch.
Yes, the word 'provides' is more explicit. I'll put this in a follow-up patch.
If this is the definitive way of implementing a virtual package, shouldn't it
be added to docs/manual/adding-packages-tips.txt?

Thanks for the review.

Best regards,
ELB

  parent reply	other threads:[~2014-02-10 13:44 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-07 13:21 [Buildroot] [PATCH v7 0/4] udev is now provided by systemd or eudev Eric Le Bihan
2014-02-07 13:21 ` [Buildroot] [PATCH v7 1/4] eudev: new package Eric Le Bihan
2014-02-07 19:14   ` Thomas De Schampheleire
2014-02-10 11:16     ` Eric Le Bihan
2014-02-07 13:21 ` [Buildroot] [PATCH v7 2/4] udev: convert to virtual package Eric Le Bihan
2014-02-07 20:17   ` Thomas De Schampheleire
2014-02-07 21:14     ` Eric Le Bihan
2014-02-07 22:56       ` Yann E. MORIN
2014-02-07 21:30   ` Samuel Martin
2014-02-10 11:22     ` Eric Le Bihan
2014-02-07 13:21 ` [Buildroot] [PATCH v7 3/4] systemd: bump to v207 Eric Le Bihan
2014-02-07 20:24   ` Thomas De Schampheleire
2014-02-07 22:00   ` Samuel Martin
2014-02-10 13:26     ` Eric Le Bihan
2014-02-10 13:44       ` Samuel Martin
2014-02-07 13:21 ` [Buildroot] [PATCH v7 4/4] manual: update /dev management section Eric Le Bihan
2014-02-07 20:26   ` Thomas De Schampheleire
2014-02-07 22:04     ` Samuel Martin
2014-02-07 20:34 ` [Buildroot] [PATCH v7 0/4] udev is now provided by systemd or eudev Arnout Vandecappelle
2014-02-07 20:39   ` Thomas De Schampheleire
2014-02-10 13:44   ` Eric Le Bihan [this message]
2014-02-10 18:25     ` Thomas Petazzoni
2014-02-12 21:34 ` Peter Korsgaard

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=20140210134415.GD22843@pc-eric \
    --to=eric.le.bihan.dev@free.fr \
    --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