mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH v2] configure_helper.py: check for emptyish ptxdist environment variables
Date: Wed, 16 Oct 2019 13:38:56 +0200	[thread overview]
Message-ID: <20191016113856.aad2nol5dsfy6pq6@pengutronix.de> (raw)
In-Reply-To: <20191016105310.w3fmq26kuahbyrob@pengutronix.de>

On Wed, Oct 16, 2019 at 12:53:10PM +0200, Roland Hieber wrote:
> Michael, any comments? It does not seem to be applied yet.

Right, this got lost. I'm not sure I like this. Why would there be an empty
PTXDIST env variable?

Michael

> On Wed, Sep 25, 2019 at 03:13:40PM +0200, Roland Hieber wrote:
> > When the environment variable exists, but is empty, os.environment.get()
> > will return its value instead of using the supplied default. Check for
> > cases like that to prevent calling an empty command.
> > 
> > Signed-off-by: Roland Hieber <rhi@pengutronix.de>
> > ---
> >  v1 -> v2:
> >   - prevent "AttributeError: 'NoneType' object has no attribute 'strip'"
> >     if none of the checked environment variables are set
> > 
> >  scripts/configure_helper.py | 7 ++++++-
> >  1 file changed, 6 insertions(+), 1 deletion(-)
> > 
> > diff --git a/scripts/configure_helper.py b/scripts/configure_helper.py
> > index c7b46f3b3846..73dd4a2add1c 100755
> > --- a/scripts/configure_helper.py
> > +++ b/scripts/configure_helper.py
> > @@ -151,7 +151,12 @@ def abort(message):
> >  	exit(1)
> >  
> >  def ask_ptxdist(pkg):
> > -	ptxdist = os.environ.get("PTXDIST", os.environ.get("ptxdist", "ptxdist"))
> > +	ptxdist = os.environ.get("PTXDIST")
> > +	if not ptxdist or not ptxdist.strip():
> > +		ptxdist = os.environ.get("ptxdist")
> > +	if not ptxdist or not ptxdist.strip():
> > +		ptxdist = "ptxdist"
> > +	
> >  	p = subprocess.Popen([ ptxdist, "-k", "make",
> >  		"/print-%s_DIR" % pkg,
> >  		"/print-%s_SUBDIR" % pkg,
> > -- 
> > 2.23.0
> > 
> > 
> > _______________________________________________
> > ptxdist mailing list
> > ptxdist@pengutronix.de
> > 
> 
> -- 
> Roland Hieber                     | r.hieber@pengutronix.de     |
> Pengutronix e.K.                  | https://www.pengutronix.de/ |
> Peiner Str. 6-8, 31137 Hildesheim | Phone: +49-5121-206917-5086 |
> Amtsgericht Hildesheim, HRA 2686  | Fax:   +49-5121-206917-5555 |
> 

-- 
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:[~2019-10-16 11:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-11  7:50 [ptxdist] [PATCH] " Roland Hieber
2019-09-23  8:46 ` Roland Hieber
2019-09-25 13:13 ` [ptxdist] [PATCH v2] " Roland Hieber
2019-10-16 10:53   ` Roland Hieber
2019-10-16 11:38     ` Michael Olbrich [this message]
2019-10-16 11:58       ` Roland Hieber
2019-10-16 13:26         ` Michael Olbrich
2019-10-17  8:24           ` Roland Hieber
2019-10-17  8:41 ` [ptxdist] [PATCH v3] configure_helper.py: be more verbose when calling ptxdist fails Roland Hieber

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=20191016113856.aad2nol5dsfy6pq6@pengutronix.de \
    --to=m.olbrich@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