Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Nelson <eric.nelson@boundarydevices.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH V5 3/3] i.MX: use temp directory for Freescale self-extractors
Date: Fri, 14 Feb 2014 13:11:58 -0700	[thread overview]
Message-ID: <52FE788E.1020408@boundarydevices.com> (raw)
In-Reply-To: <20140214190352.GA3428@free.fr>

Thanks Yann,

On 02/14/2014 12:03 PM, Yann E. MORIN wrote:
> Eric, All,
>
> On 2014-02-13 17:26 -0700, Eric Nelson spake thusly:
>> The Freescale packages imx-lib, libfslcodec, libfslparser, and libfslvpuwrap
>> are each bundled as self-extracting tar-balls that contain a shell script
>> and a EULA in their package headers.
>>
>> These self-extractors also contain a command to create the destination
>> directory using "mkdir" (no -p) prior to extraction.
>>
>> Since we want to place the output into the build directory, which has already
>> been created at the time of extraction, this causes a warning message
>> from "mkdir".
>>
>> This patch changes things so that each package is extracted first into a
>> sub-directory, and the content is moved into the eventual build directory.
>
> In fact, I was not clear in my previous reply: as your testing shows,
> and as Arnout suggested, we can well leave with this warning.
>

That works for me.

> So, to make it clear this time: I don;t think we should try to play it
> smart with this whole directory mess: the archives do extract in a
> properly-named directory, so lets just accept the little warning.
>
Cool.

I have contacted Freescale to see if we can at least get "mkdir -p" into
the next release, and hopefully also address the awk-wardness of
extracting the EULA.

> The changes introduced by this patch, although not too complex, are not
> trivial either.
>

Agreed. This is a lot of change for a couple of small warnings.

> I suggest we just drop this patch, unless Peter really wants it.
>

+1

> Sorry I was not explicit enough in my previous mail. Thank you for
> staying with us all along the journey! :-)

I'm glad to help.

Regards,


Eric

  reply	other threads:[~2014-02-14 20:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-14  0:26 [Buildroot] [PATCH V5 0/3] i.MX: Updates to Freescale acceleration Eric Nelson
2014-02-14  0:26 ` [Buildroot] [PATCH V5 1/3] i.MX: Use FREESCALE_IMX_SITE for Freescale packages Eric Nelson
2014-02-14 20:16   ` Peter Korsgaard
2014-02-14  0:26 ` [Buildroot] [PATCH V5 2/3] i.MX: Update versions to match latest Freescale release Eric Nelson
2014-02-14 20:19   ` Peter Korsgaard
2014-02-14  0:26 ` [Buildroot] [PATCH V5 3/3] i.MX: use temp directory for Freescale self-extractors Eric Nelson
2014-02-14  8:25   ` Thomas Petazzoni
2014-02-14 15:18     ` Eric Nelson
2014-02-14 19:03   ` Yann E. MORIN
2014-02-14 20:11     ` Eric Nelson [this message]
2014-02-14 20:20       ` Peter Korsgaard

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=52FE788E.1020408@boundarydevices.com \
    --to=eric.nelson@boundarydevices.com \
    --cc=buildroot@busybox.net \
    /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