Arch Linux User Repository

TL;DR

Upgrade using aur/yay might take very long and works inefficiently.

Upgrade using aur/paru requires the -d flag.

This is not my fault.

Note to the lovers of AUR helpers : It looks like dependency resolution is a complex topic. Despite all package relations being properly declared in the Flutter packages, most AUR helpers seem to have trouble resolving the dependency chain between the package bases aur/flutter and aur/flutter-artifacts-google-bin. This is not my fault and I cannot do anything about it.

It looks like the initial installation works fine using aur/paru. Sadly aur/paru does not reach at building updates for the package without additional flags. Please use paru -Syud (whereas the -d is the relevant flag) to upgrade the package.

On the other hand aur/yay properly reaches at both installing and updating this package, even though it builds the package 15 times (!!!) again and again.

If you use aur/paru, consider to simply execute pacman -R flutter && pacman -Rns flutter to clean up the previous installation of both package bases.

• https://github.com/Jguer/yay/issues/2413
• https://github.com/Morganamilo/paru/issues/1173

If you build both package bases using makepkg -sfC and later on install all build outputs using pacman -U, both the installation and the updates work like a charm.

I'm very sorry for the inconvenience, but sadly there's nothing I can do about this.

Huge update to the Flutter AUR package :

The previous implementation basically did a user installation of Flutter - downloaded the custom Dart SDK, CI artifacts from Chromium CI and had to be kept in user R/W access in order to have the Flutter Cache Manager working.

These times are now over - a clean and (almost) completely rewritten PKGBUILD which now uses clean dependency declarations, system Dart and Gradle and for sure no more user R/W installation directory.

This AUR entry is now a split package. Installing aur/flutter will still bundle the entire toolchain you knew from before. The other way round, if you don't need everything - e.g. when depending on Flutter as a build dependency in another package, you can choose to only depend on what you need.

The following split packages are available :

• flutter : meta package containing all other split packages

• flutter-common : the common files for Flutter needed for all use cases

• flutter-devel : your option of choice as a developer - ships the Flutter tool and all required templates to e.g. create a new project

• flutter-tool : The pure Flutter tool. Use as depends to build your package.

• flutter-target-linux : The Flutter Linux build files. Use as depends to build your package.

• flutter-target-web : The Flutter web build files. Use as depends to build web apps (e.g. fluffychat-web does this).

• flutter-target-android : The Flutter Android build files. Use if you want to develop Android apps.

• flutter-gradle : The Flutter Gradle wrapper. Populated from system Gradle.

• flutter-intellij-patch : a tiny patch to make the IntelliJ Flutter plugin work with the new package.

• flutter-material-fonts-google-bin : Mandatory fonts package, planned to have a system-installed drop-in replacement soon.

• flutter-engine-common-google-bin : Shared part of the Flutter engine - downloaded from Google servers.

• flutter-sky-engine-google-bin : Flutter sky engine - downloaded from Google servers.

• flutter-engine-linux-google-bin : Linux part of the Flutter engine - downloaded from Google servers.

• flutter-engine-web-google-bin : Web part of the Flutter engine - downloaded from Google servers.

• flutter-engine-android-google-bin : Android part of the Flutter engine - downloaded from Google servers.

• flutter-gradle-google-bin : The Flutter Gradle wrapper - downloaded from Google servers.

• flutter-dart-google-bin : The Flutter original Dart SDK - downloaded from Google servers. This is helpful if the extra/dart package is not available in the right version on your distro or remix.

Stay tuned for non google-bin versions of the engine, they are in coming !

Since almost everything is written from scratch and heavy patches are applied to use the system packages as dependencies, there might still be bugs occurring. Please report them otherwise I can't fix them !

I opened a PR to update this: https://github.com/frealgagu/archlinux.flutter/pull/9

This package was flagged out of date on the 4th of May for not releasing the 2.0.6 update; however, the 2.0.6 Flutter release was a hotfix for a bug on macOS and it doesn't concern GNU/Linux.

Form Flutter's official Github page:

2.0.6 (April 16, 2021)

This is a hotfix release that addresses a single issue:

• Issue #81326 - macOS binaries not codesigned There are no code changes to this release, but binary artifacts for macOS were re-built and codesigned.

.git is required by the CLI tool. The others aren't required, but if you mutate the checkout then the flutter upgrade command won't work.

Are the .git/, .github/, .idea/ folders really required? They are massive (over 135MiB) and seems to have no use at all. Shouldn't the PKGBUILD leave those out of the install process?

I had the same problem as hossamdash and following his solution fixed it.

I had the same problem as hossamdash and following his solution fixed it.

flutter-dev is now orphaned, didn't you think about taking it?

so i have installed this package but was facing two issues: Although i had the dart package installed on my system -which this package depends on-, both installing this package for the first time and each flutter doctor -v command results in the redownload of the dark-sdk which is inside /opt/flutter/bin/cache disregarding both the existing dark-sdk in the cache and the standalone dart package installed on my system. to solve this i did two things, i uninstalled the standalone dart sdk and then added a line to the build files of this package right after the chmod -R g+w /opt/flutter line. this line is chmod g+s /opt/flutter makes any files created within the /opt/flutter path inherit the group flutterusers which stops flutter doctor from redownloading the dart-sdk.

I think that flutter is designed to be self-upgraded. Hence in the end I decided to clone flutter repo instead of using AUR.

Getting failed to commit transaction error.

Using the --overwrite /opt/flutter/packages/flutter_tools/.packages option solves the issue, but the question is, is it fine to overwrite?