From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] dl_dir problem with building using legal-info
Date: Mon, 1 Apr 2019 17:47:51 +0200 [thread overview]
Message-ID: <20190401174751.581e16a4@windsurf> (raw)
In-Reply-To: <9f90c933-8494-9a82-ab12-7f67873fda9e@ginzinger.com>
Martin,
On Mon, 1 Apr 2019 15:56:55 +0200
Martin Kepplinger <martin.kepplinger@ginzinger.com> wrote:
> It seems like the plan might be to move from one "dl" directory
> containing the tarballs, old_dl_dir, to the per-package directories in "dl".
>
> So: I reuse the tarballs in "legal-info" for building. (think: no
> internet connection). legal-info contains directories *with versions*.
> In any case, it's easy by finding all archives and copying them to "dl"
> before building.
>
> If old_dl_dir would be removed from the download scripts, this would
> break for me. The per-package directories in "dl" *don't contain
> versions* and I guess there's no trivial way to recreate this directory
> structure. So I thought I'd talk about this before old_dl_dir is gone...
>
> In short: Before removing to look in old_dl_dir, please don't break this
> use-case :) Is there an even better way to build using legal-info that
> I'm not aware of already? If not, what could we implement?
Why don't you use "make source" ? That's the intended target to
populate the dl/ directory with everything that is needed to do a build
with no internet connection.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-04-01 15:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-01 13:56 [Buildroot] dl_dir problem with building using legal-info Martin Kepplinger
2019-04-01 15:47 ` Thomas Petazzoni [this message]
2019-04-02 4:48 ` Martin Kepplinger
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=20190401174751.581e16a4@windsurf \
--to=thomas.petazzoni@bootlin.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.