All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH next] package/pkg-luarocks: use <pkg>_EXTRACT_DEPENDENCIES
Date: Fri, 16 Nov 2018 20:25:36 +0100	[thread overview]
Message-ID: <87h8ggsu33.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20181116135300.27234-1-thomas.petazzoni@bootlin.com> (Thomas Petazzoni's message of "Fri, 16 Nov 2018 14:53:00 +0100")

>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@bootlin.com> writes:

 > The host luarocks tool is needed when *extracting* luarocks
 > packages. Since regular dependencies are only available at the
 > configure step, it caused the "luarocks" program to be available too
 > late to be used to extract luarocks packages.

 > To work around this, host-luarocks was manually added as a dependency
 > of the extract step of luarocks packages. While this worked fine until
 > now, it breaks badly with per-package folders, because host-luarocks
 > is not recorded as an extract dependency of luarocks packages, and
 > therefore is not copied to the per-package host folder, causing a
 > failure.

 > In the mean time, the <pkg>_EXTRACT_DEPENDENCIES mechanism was added,
 > which aims at fixing exactly this problem, so let's use it and
 > simplify pkg-luarocks.mk.

 > Cc: Francois Perrad <francois.perrad@gadz.org>
 > Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>

Committed to next, thanks.

-- 
Bye, Peter Korsgaard

      parent reply	other threads:[~2018-11-16 19:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-16 13:53 [Buildroot] [PATCH next] package/pkg-luarocks: use <pkg>_EXTRACT_DEPENDENCIES Thomas Petazzoni
2018-11-16 15:08 ` Yann E. MORIN
2018-11-16 17:41 ` François Perrad
2018-11-16 19:25 ` Peter Korsgaard [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=87h8ggsu33.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.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 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.