Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Adam Duskett <aduskett@gmail.com>
Cc: Luca Ceresoli <luca@lucaceresoli.net>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] Flutter-engine package help wanted.
Date: Mon, 17 Jul 2023 21:16:52 +0200	[thread overview]
Message-ID: <20230717191652.GB1080294@scaer> (raw)
In-Reply-To: <20230717183817.GA1080294@scaer>

Adam, All,

Folloing our discussion on IRC, it turns out that I got it partly
(mostly) wrong.

On 2023-07-17 20:38 +0200, Yann E. MORIN spake thusly:
> On 2023-07-14 20:02 -0700, Adam Duskett spake thusly:

So, we do not need to download anything from the flutter repo; we just
need a file, .gclient, that contains directives for gclient to perform
the actual download.

As an aside, gclient is like repo (another google tool, I guess), right?

So, basically, what you did in your .mk looks like I would have done,
except no using _DL_DIR as a scratch-dir to do the download, but in a
sub-dir of the package dir (see my previous reply).

Finally: gclient runs git-clone, we can't have stability in that, it's
not reproducible.

If the .git dirs really need to be present at configure/build time,
we're borked, we can't hash the generated tarball.

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2023-07-17 19:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-15  3:02 [Buildroot] Flutter-engine package help wanted Adam Duskett
2023-07-15 16:24 ` Peter Korsgaard
2023-07-15 18:35   ` Adam Duskett
2023-07-15 21:45     ` Peter Korsgaard
2023-07-16 15:32 ` Arnout Vandecappelle via buildroot
2023-07-17 17:44   ` Adam Duskett
2023-07-17 18:38 ` Yann E. MORIN
2023-07-17 19:16   ` Yann E. MORIN [this message]
2023-07-17 19:33     ` Adam Duskett
2023-07-19  2:04       ` Adam Duskett
2023-07-20  2:12         ` Adam Duskett

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=20230717191652.GB1080294@scaer \
    --to=yann.morin.1998@free.fr \
    --cc=aduskett@gmail.com \
    --cc=buildroot@buildroot.org \
    --cc=luca@lucaceresoli.net \
    --cc=thomas.petazzoni@bootlin.com \
    /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