All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Romain Naour <romain.naour@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 3/5] package/efl: rework eeze handling in Kconfig
Date: Sun, 30 Jan 2022 21:44:43 +0100	[thread overview]
Message-ID: <20220130214443.0106ce53@windsurf> (raw)
In-Reply-To: <400c4077-1e25-a5fd-592e-cbf149d7a626@gmail.com>

Hello,

On Sun, 30 Jan 2022 18:40:39 +0100
Romain Naour <romain.naour@gmail.com> wrote:

> Le 30/01/2022 à 15:02, Thomas Petazzoni a écrit :
> > On Sat, 29 Jan 2022 23:46:49 +0100
> > Romain Naour <romain.naour@gmail.com> wrote:
> >   
> >> Commit [1] added eeze dependency using "depends on" to several efl
> >> options (drm, libmount) instead of selecting eeze and propagate the
> >> udev reverse dependency.  
> > 
> > I do agree with changing from a "depends on BR2_PACKAGE_EFL_EEZE" to a
> > "depends BR2_PACKAGE_HAS_UDEV" + "select BR2_PACKAGE_EFL_EEZE".
> > However...
> >   
> >> The dependency between eeze, libinput, efl drm requires to add a new
> >> libinput option.  
> > 
> > ... I don't understand this justification. Could you clarify. Even
> > after reading PATCH 4/5, I don't get the relationship. PATCH 4/5 could
> > have been done (I guess using the same principle of "depends on
> > BR2_PACKAGE_EFL_EEZE".  
> 
> AFAIK, efl drm needs libinput (elput) that requires udev (eeze).
> Until now we don't have a libinput option to disable it when eeze is also disabled.

Right, and? How is that related to changing "depends on
BR2_PACKAGE_EFL_EEZE" to "select BR2_PACKAGE_EFL_EEZE" ?

> >> Rework eeze handling to use select BR2_PACKAGE_EFL_EEZE since the
> >> user is already aware of the udev dependency (BR2_PACKAGE_HAS_UDEV).  
> > 
> > I don't understand why you say the user is already aware of the udev
> > dependency? Thanks to the comments?  
> 
> I mean if eeze can be selected, it means that the used either selected systemd
> or eudev.

But that's just normal thing in Buildroot, no? I fail to understand this
part of your commit log.

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2022-01-30 20:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-29 22:46 [Buildroot] [PATCH 1/5] package/efl: bump to version 1.26.1 Romain Naour
2022-01-29 22:46 ` [Buildroot] [PATCH 2/5] package/enlightenment: bump to version 0.25.1 Romain Naour
2022-01-30 14:00   ` Thomas Petazzoni via buildroot
2022-01-29 22:46 ` [Buildroot] [PATCH 3/5] package/efl: rework eeze handling in Kconfig Romain Naour
2022-01-30 14:02   ` Thomas Petazzoni via buildroot
2022-01-30 17:40     ` Romain Naour
2022-01-30 20:44       ` Thomas Petazzoni via buildroot [this message]
2022-01-29 22:46 ` [Buildroot] [PATCH 4/5] package/efl: handle input option Romain Naour
2022-01-30 14:05   ` Thomas Petazzoni via buildroot
2022-01-29 22:46 ` [Buildroot] [PATCH 5/5] docs/manual/adding-packages-directory.txt: reorder select/depends Romain Naour
2022-01-30 14:12   ` Thomas Petazzoni via buildroot
2022-01-30 14:00 ` [Buildroot] [PATCH 1/5] package/efl: bump to version 1.26.1 Thomas Petazzoni via buildroot

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=20220130214443.0106ce53@windsurf \
    --to=buildroot@buildroot.org \
    --cc=romain.naour@gmail.com \
    --cc=thomas.petazzoni@bootlin.com \
    /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.