Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Hongxu Jia <hongxu.jia@windriver.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-networking][PATCH] networkmanager: goodbye libnm-glib
Date: Mon, 1 Jul 2019 15:55:29 +0300	[thread overview]
Message-ID: <20190701125529.GB7483@localhost> (raw)
In-Reply-To: <0b346c3b-22e5-2e09-3a81-d199e5c8591a@windriver.com>

On Fri, Jun 28, 2019 at 10:57:02PM +0800, Hongxu Jia wrote:
> On 6/28/19 6:07 PM, Adrian Bunk wrote:
> > On Thu, Jun 27, 2019 at 09:47:49AM -0400, Hongxu Jia wrote:
> > > Since commit [061953143 networkmanager: Update to 1.18.0] applied,
> > > upstream disable libnm-glib by default. And in further networkmanager,
> > > upstream removes libnm-glib, libnm-glib-vpn, and libnm-util for good
> > > ...
> > Any strong reason for removing this already now?
> 
> Make sure to clean up empty package, in 1.18
> 
> libnm-glib is already disabled, and left three empty
> 
> packages(no package generated acturally). I found
> 
> the issue, trace the reason and provide fix

What problem does this issue cause?

> You may note original PACKAGECONFIG[glib] does not have
> 
> without option, so clean up it rather than add missing without option
> 
> PACKAGECONFIG[glib] = "--with-libnm-glib,,dbus-glib-native dbus-glib"

That is actually fine and doesn't need a fix - the library is only built 
if explicitely requested --with-libnm-glib.

> > It's gone in 1.20 so removal then is clear, but if someone wants
> > to use it for legacy code with 1.18 this should stay possible as
> > long as <= 1.18 is shipped.
> 
> I think it will be upgraded 1.20 soon, and if someone wants
> 
> to use legacy code, I think 1.16 in warrior is better choose
> 
> which libnm-glib is always enabled

"soon" might be after Yocto 2.8 branches.

> //Hongxu

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



  reply	other threads:[~2019-07-01 12:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-27 13:47 [meta-networking][PATCH] networkmanager: goodbye libnm-glib Hongxu Jia
2019-06-28 10:07 ` Adrian Bunk
2019-06-28 14:57   ` Hongxu Jia
2019-07-01 12:55     ` Adrian Bunk [this message]
2019-07-02  1:27       ` Hongxu Jia
2019-07-02  1:35       ` Hongxu Jia
2019-07-09 17:40     ` Khem Raj
2019-07-10  1:20       ` Hongxu Jia

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=20190701125529.GB7483@localhost \
    --to=bunk@stusta.de \
    --cc=hongxu.jia@windriver.com \
    --cc=openembedded-devel@lists.openembedded.org \
    /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