All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/7] package/pmake: add host pmake
Date: Wed, 30 Jan 2013 23:43:21 +0100	[thread overview]
Message-ID: <201301302343.22202.yann.morin.1998@free.fr> (raw)
In-Reply-To: <20130130233222.54f9173e@skate>

Thomas, Arnout, All,

On Wednesday 30 January 2013 Thomas Petazzoni wrote:
> Dear Arnout Vandecappelle,
> 
> On Wed, 30 Jan 2013 17:55:59 +0100, Arnout Vandecappelle wrote:
> 
> >   Doesn't it?  It seems to work for liblockfile...
> 
> Does it really work properly?
> 
> In the past, a tarball was directly fed into patch, which was finding
> some patch contents and that's it. Since then, the apply-patches.sh
> script has been reworked to properly apply the patches within a
> tarball, but I don't think it applies patches that are contained in
> a debian/patches/ directory.

Ah, I missed that. Indeed it works.

What happens (eek! apply-patches.sh is hard to read) is that, if a patch
is neamd like a tarball, it is extracted in a temp dir, and that temp dir
is scanned as if it was passed as arg to apply-patches.sh:

---8<---
elif echo "$i" | grep -q -E "\.tar(\..*)?$|\.tbz2?$|\.tgz$" ; then
    unpackedarchivedir="$builddir/.patches-$(basename $i)-unpacked"
    rm -rf "$unpackedarchivedir" 2> /dev/null
    mkdir "$unpackedarchivedir"
    tar -C "$unpackedarchivedir" -xaf "${path}/$i"
    scan_patchdir "$unpackedarchivedir"
---8<---

So, yes, it works. Yet, I still find it a bit ugly (but less so than I
initially suspected). And it is not documented.

Should this be considered a feature? Can we rely on it?

If so, then I'll update the doc accordingly.

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2013-01-30 22:43 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-29 22:33 [Buildroot] [pull request v3] Pull request for branch yem-new-packages Yann E. MORIN
2013-01-29 22:33 ` [Buildroot] [PATCH 1/7] package/usbredir: update to version 0.6 Yann E. MORIN
2013-01-29 22:33 ` [Buildroot] [PATCH 2/7] package/pmake: add host pmake Yann E. MORIN
2013-01-30  7:52   ` Arnout Vandecappelle
2013-01-30 13:13     ` Yann E. MORIN
2013-01-30 13:24       ` Thomas Petazzoni
2013-01-30 14:34         ` Yann E. MORIN
2013-01-30 14:49           ` Thomas Petazzoni
2013-01-30 18:50             ` Yann E. MORIN
2013-01-30 16:55       ` Arnout Vandecappelle
2013-01-30 22:32         ` Thomas Petazzoni
2013-01-30 22:43           ` Yann E. MORIN [this message]
2013-01-30 22:47             ` Arnout Vandecappelle
2013-01-30 23:20               ` Yann E. MORIN
2013-01-30 22:36         ` Yann E. MORIN
2013-01-29 22:33 ` [Buildroot] [PATCH 3/7] package/libbsd: new package Yann E. MORIN
2013-01-29 22:33 ` [Buildroot] [PATCH 4/7] package/libedit2: " Yann E. MORIN
2013-01-29 22:33 ` [Buildroot] [PATCH 5/7] package/ceph: " Yann E. MORIN
2013-01-29 22:33 ` [Buildroot] [PATCH 6/7] package/dtc: " Yann E. MORIN
2013-01-29 22:33 ` [Buildroot] [PATCH 7/7] package/dtc: add option to install programs Yann E. MORIN
2013-02-03 13:40 [Buildroot] [pull request v4] Pull request for branch yem-new-packages Yann E. MORIN
2013-02-03 13:40 ` [Buildroot] [PATCH 2/7] package/pmake: add host pmake Yann E. MORIN
2013-02-04 16:01 [Buildroot] [pull request v5] Pull request for branch yem-new-packages Yann E. MORIN
2013-02-04 16:01 ` [Buildroot] [PATCH 2/7] package/pmake: add host pmake Yann E. MORIN
2013-02-04 18:54   ` Arnout Vandecappelle
2013-02-06 18:51     ` Yann E. MORIN

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=201301302343.22202.yann.morin.1998@free.fr \
    --to=yann.morin.1998@free.fr \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.