Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Stephan Hoffmann <sho@relinux.de>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] pkg-infra: add <pkg>-extract and	<pkg>-patch targets to OVERRIDE support
Date: Fri, 07 Dec 2012 11:32:24 +0100	[thread overview]
Message-ID: <50C1C5B8.2020505@relinux.de> (raw)
In-Reply-To: <874njy1x58.fsf@dell.be.48ers.dk>

Am 07.12.2012 02:14, schrieb Peter Korsgaard:
>>>>>> "Arnout" == Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> writes:
> Hi,
>
>  Arnout> From: "Arnout Vandecappelle (Essensium/Mind)" <arnout@mind.be>
>  Arnout> The legal-info target (and possibly others as well) depends on
>  Arnout> <pkg>-extract to make sure the license file is available.  However,
>  Arnout> when <PKG>_OVERRIDE_SRCDIR is active, the <pkg>-extract target
>  Arnout> doesn't exist.
>
>  Arnout> To solve this, we add <pkg>-extract which depends on <pkg>-rsync.
>  Arnout> While we're at it, we do the same for <pkg>-patch.  That avoids the
>  Arnout> same problem in the future if something starts depending on
>  Arnout> <pkg>-patch.
>
>  Arnout> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
>  Arnout> Acked-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
>  Arnout> Acked-by: Luca Ceresoli <luca@lucaceresoli.net>
>
> Committed, thanks.
>
Thanks, now legal info works together with OVERRIDE.

Stephan


-- 
reLinux     -    Stephan Hoffmann
Am Schmidtgrund 124    50765 K?ln
Tel. +49.221.95595-19    Fax: -64
www.reLinux.de     sho at reLinux.de

      reply	other threads:[~2012-12-07 10:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-06 23:16 [Buildroot] [PATCH] pkg-infra: add <pkg>-extract and <pkg>-patch targets to OVERRIDE support Arnout Vandecappelle
2012-12-07  1:14 ` Peter Korsgaard
2012-12-07 10:32   ` Stephan Hoffmann [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=50C1C5B8.2020505@relinux.de \
    --to=sho@relinux.de \
    --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