Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Issue with the luarocks infra and legal-info
Date: Sat, 1 Mar 2014 16:50:18 +0100	[thread overview]
Message-ID: <20140301165018.2743ec23@skate> (raw)

Hello Fran?ois,

I've discovered an issue with the luarocks package infrastructure that
apparently we didn't notice during its review. The problem is that the
luarocks package infrastructure makes the extract step of a lua package
depend on host-luarocks.

The problem with this is that the legal-info infrastructure does run
the extract step of all packages in order to extract their source code
and get the license files. In the case of luarocks packages, this
triggers the build of host-luarocks, itself triggering the build of
host-lua and the selected lua-interpreter. But lua-interpreter is a
target package, so it depends on the toolchain, so the toolchain is
also built. This is rather annoying for the legal-info make target,
which should be relatively quick and normally not build anything or
only small things.

Is there anything that can be done to improve this? Does host-luarocks
really need to depend on the target lua interpreter?

Thanks in advance for your suggestions,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

             reply	other threads:[~2014-03-01 15:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-01 15:50 Thomas Petazzoni [this message]
2014-03-01 18:23 ` [Buildroot] [UNSURE]Issue with the luarocks infra and legal-info François Perrad
2014-03-01 18:41   ` Thomas Petazzoni

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=20140301165018.2743ec23@skate \
    --to=thomas.petazzoni@free-electrons.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