Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Luca Ceresoli <luca@lucaceresoli.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] qpid-proton: new package
Date: Sat, 11 Jul 2015 15:17:14 +0200	[thread overview]
Message-ID: <55A1175A.2080401@lucaceresoli.net> (raw)
In-Reply-To: <55A04632.4050508@mind.be>

Dear Arnout,

Arnout Vandecappelle wrote:
> On 07/10/15 18:10, Luca Ceresoli wrote:
>> Note: the tarball is buggy, as is contains two leading components instead of
>> one, the first being a dummy ".":
>>
>>    $ tar taf ~/src/qpid-proton-0.9.1.tar.gz
>>    ./
>>    ./qpid-proton-0.9.1-rc1/
>>    ./qpid-proton-0.9.1-rc1/version.txt
>
>   Would it make sense to add an <PKG>_STRIP_COMPONENTS variable to handle this
> case? There are a few other packages that have this problem.

Indeed! Four packages have the opposite problem and need to force
--strip-components=0: intel-microcode, nanocom, tzdata and zic.

Thus, yes, it makes sense. I'll have a look.

-- 
Luca

      reply	other threads:[~2015-07-11 13:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-10 16:10 [Buildroot] [PATCH] qpid-proton: new package Luca Ceresoli
2015-07-10 22:24 ` Arnout Vandecappelle
2015-07-11 13:17   ` Luca Ceresoli [this message]

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=55A1175A.2080401@lucaceresoli.net \
    --to=luca@lucaceresoli.net \
    --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