Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH v2] TI tools - make EULA unpack work when /opt is writeable
Date: Sat, 09 Oct 2010 08:52:20 -0600	[thread overview]
Message-ID: <4CB081A4.9010908@mlbassoc.com> (raw)
In-Reply-To: <4C78D1E1.9080101@mlbassoc.com>

On 08/28/2010 03:07 AM, Gary Thomas wrote:
> This patch addresses the problem where the TI tools that need
> the EULA unpack into the wrong place if the user has write
> permission in /opt. The current behaviour of expecting the
> unpacker to fall back to the $HOME environment variable should
> not be relied on. The patch changes the unpack step to use
> the --prefix= option which will always work.
>
> Version 2:
> * Update patch to be against org.openembedded.dev branch
> * Incorporate full description into patch

What about this patch?  It's been nearly 6 weeks and no discussion
or anything.

The problem persists in today's tree.

n.b. there was a discussion about automatic application of a patch
if it goes more than two weeks without objection.  What about that??

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------



  reply	other threads:[~2010-10-09 14:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-28  9:07 [PATCH v2] TI tools - make EULA unpack work when /opt is writeable Gary Thomas
2010-10-09 14:52 ` Gary Thomas [this message]
2010-11-06 14:11   ` Stefan Schmidt
2010-11-07  9:05     ` Koen Kooi
2010-11-07 11:25       ` Stefan Schmidt
2010-11-15  8:46       ` Frans Meulenbroeks
2010-11-16 23:31     ` Maupin, Chase

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=4CB081A4.9010908@mlbassoc.com \
    --to=gary@mlbassoc.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