mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: "Jan Lübbe" <jlu@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] networkmanager: update to release 0.9.4.0
Date: Thu, 31 May 2012 15:11:08 +0200	[thread overview]
Message-ID: <1338469868.2872.4.camel@coredoba.hi.pengutronix.de> (raw)
In-Reply-To: <201205311503.27256.jbe@pengutronix.de>

On Thu, 2012-05-31 at 15:03 +0200, Juergen Beisert wrote:
> Jan Luebbe wrote:
> > Also include changes by Juergen Beisert <jbe@pengutronix.de>
> > to correct configure options and the missing iptables dependency.
> >
> > Signed-off-by: Jan Luebbe <jlu@pengutronix.de>
> > ---
> >  rules/networkmanager.in   |    5 ++++-
> >  rules/networkmanager.make |   31 ++++++++++++++++++++++++-------
> >  2 files changed, 28 insertions(+), 8 deletions(-)
> >
> > diff --git a/rules/networkmanager.in b/rules/networkmanager.in
> > index 2c08fea..0397918 100644
> > --- a/rules/networkmanager.in
> > +++ b/rules/networkmanager.in
> > @@ -10,10 +10,13 @@ menuconfig NETWORKMANAGER
> >  	select DBUS_GLIB
> >  	select LIBNL
> >  	select LIBUUID
> > -	select WPA_SUPPLICANT
> > +	select WPA_SUPPLICANT			if RUNTIME
> >  	select GNUTLS
> >  	select HOST_INTLTOOL
> >  	select DBUS_PYTHON                      if NETWORKMANAGER_EXAMPLES
> > +	select IPTABLES
> 
> IPTABLES could also use a "if RUNTIME"?

Makes sense.

> > +# for the 'iptables' tool
> > +	select IPTABLES_IPV4
> >  	prompt "networkmanager                "
> >  	help
> >  	  NetworkManager is a tool to automate network configuration as far as
> > diff --git a/rules/networkmanager.make b/rules/networkmanager.make
> > index 32d11ed..e9b38fd 100644
> > --- a/rules/networkmanager.make
> > +++ b/rules/networkmanager.make
> > @@ -17,8 +17,8 @@ PACKAGES-$(PTXCONF_NETWORKMANAGER) += networkmanager
> >  #
> >  # Paths and names
> >  #
> > -NETWORKMANAGER_VERSION	:= 0.9.2.0
> > -NETWORKMANAGER_MD5	:= d7dce01e97758253bc4ed81d7b86045f
> > +NETWORKMANAGER_VERSION	:= 0.9.4.0
> > +NETWORKMANAGER_MD5	:= 66a54b51a4998c484613911b72a7e6ff
> >  NETWORKMANAGER		:= NetworkManager-$(NETWORKMANAGER_VERSION)
> >  NETWORKMANAGER_SUFFIX	:= tar.xz
> >  NETWORKMANAGER_URL	:=  http://ftp.gnome.org/pub/GNOME/sources/NetworkManager/0.9/$(NETWORKMANAGER).$(NETWORKMANAGER_SUFFIX)
> >  @@ -48,7 +48,12 @@ NETWORKMANAGER_CONF_OPT := \ 
> >  	--without-docs \
> >  	--with-gnu-ld \
> >  	--with-crypto=gnutls \
> > -	--with-distro=debian
> > +	--with-distro=debian \
> > +	--with-session-tracking=none \
> > +	--with-dhclient=/sbin/dhclient \
> 
> If you enable dhclient, you also should ensure it is part of the run-time
> filesystem by a "select".

This is ensured by the select on DHCP_CLIENT.

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |


-- 
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2012-05-31 13:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-31 12:23 Jan Luebbe
2012-05-31 13:03 ` Juergen Beisert
2012-05-31 13:11   ` Jan Lübbe [this message]
2012-05-31 13:47     ` Juergen Beisert

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=1338469868.2872.4.camel@coredoba.hi.pengutronix.de \
    --to=jlu@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    /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