All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: Adam Duskett <adam.duskett@amarulasolutions.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v4 1/1] package/flutter-sdk-bin/Config.in.host: change flutter-pub-cache location
Date: Sat, 03 Feb 2024 12:24:38 +0100	[thread overview]
Message-ID: <87a5ohu6x5.fsf@48ers.dk> (raw)
In-Reply-To: <20240113194950.11170-1-adam.duskett@amarulasolutions.com> (Adam Duskett's message of "Sat, 13 Jan 2024 12:49:50 -0700")

>>>>> "Adam" == Adam Duskett <adam.duskett@amarulasolutions.com> writes:

 > When running the command "flutter pub get," the plugins are stored in the
 > pub-cache directory along with their sha256sum hashes. The default location of
 > the pub-cache directory is current $(HOST_DIR)/share/flutter/sdk/.pub-cache,
 > which is not an acceptable choice by default because every plugin is
 > re-downloaded during every build of a flutter application either during a new
 > build or when building with the per-package-directory option enabled.

 > Furthermore, keeping the pub-cache in its current location prevents users from
 > committing the pub-cache directory to git for faster rebuilds of a
 > Buildroot-based system, as users cannot store the pub-cache for later use.

 > To fix the above issue completely, the following two changes must occur:

 >   - Change the hard-coded Flutter pub-cache location to
 >     $(DL_DIR)/br-flutter-pub-cache.

 >   - Remove the `rm -rf $(HOST_FLUTTER_SDK_BIN_SDK)/.pub-cache` and the
 >     associated comment about why the build system removes the .pub-cache
 >     directory. After further research, the help text of the precache command
 >     reads, "Populate the Flutter tool's cache of binary artifacts."
 >     The current reasoning listed in the comments is not accurate for a
 >     the following reasons:

 >     1. We do not want to remove their directory if users already have a pub
 >        cache they have symlinked to.

 >     2. If the flutter-sdk-bin package previously set up the pub-cache, then
 >        the pub-cache directory is set up with the options we want, and there
 >        is no reason to remove the pub-cache directory.

 > Signed-off-by: Adam Duskett <adam.duskett@amarulasolutions.com>
 > ---
 > changes v3 -> v4:
 >   - Hardcode the directory to $(DL_DIR)/br-flutter-pub-cache. [Yann]
 >   - Remove the `rm -rf $(HOST_FLUTTER_SDK_BIN_SDK)/.pub-cache` line. [Yann]
 >   - Remove the associated comments about the above line. [Yann]
 >   - Expand the commit log.

Committed to 2023.11.x, thanks.

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      parent reply	other threads:[~2024-02-03 18:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-13 19:49 [Buildroot] [PATCH v4 1/1] package/flutter-sdk-bin/Config.in.host: change flutter-pub-cache location Adam Duskett
2024-01-20 20:35 ` Yann E. MORIN
2024-02-03 11:24 ` 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=87a5ohu6x5.fsf@48ers.dk \
    --to=peter@korsgaard.com \
    --cc=adam.duskett@amarulasolutions.com \
    --cc=buildroot@buildroot.org \
    /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.