From: Adrian Bunk <bunk@stusta.de>
To: Trevor Gamblin <trevor.gamblin@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: inotify-tools: move recipe to oe-core from meta-oe
Date: Tue, 29 Oct 2019 23:13:31 +0200 [thread overview]
Message-ID: <20191029211331.GB26658@localhost> (raw)
In-Reply-To: <20191029203921.17227-1-trevor.gamblin@windriver.com>
On Tue, Oct 29, 2019 at 03:39:21PM -0500, Trevor Gamblin wrote:
> An interface for inotify already exists through pyinotify,
> but migrating inotify-tools to oe-core provides an option
> that doesn't rely on python.
>...
pyinotify is in meta-python.
The only option currently in oe-core is to use C,
which is the standard way to use inotify.
inotify-tools can be useful, but I don't see the rationale
why it should move from meta-oe to oe-core.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2019-10-29 21:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-29 20:39 inotify-tools: move recipe to oe-core from meta-oe Trevor Gamblin
2019-10-29 21:13 ` Adrian Bunk [this message]
2019-10-29 22:47 ` Randy MacLeod
2019-10-30 0:06 ` Trevor Gamblin
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=20191029211331.GB26658@localhost \
--to=bunk@stusta.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=trevor.gamblin@windriver.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox