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 !

btw, 2.8.1 already. And I wanna show you my update function without AUR pkg.

u() {
  # ...
  asdf update
  asdf plugin update --all
  asdf install flutter latest
  asdf global flutter latest
  export DART_SDK=$(asdf where flutter)/bin/cache/dart-sdk
  # ...
}

Also you can upgrade flutter over flutter (if you install it from flutter.dev) - flutter upgrade and even flutter downgrade, also you can change channel for upgrade/downgrade (example flutter channel {stable|beta|dev|master}; flutter upgrade) https://docs.flutter.dev/development/tools/sdk/upgrading

thank you for the 2.8 update @frealgagu

@romjan1412 a little busy with zero-day log4j vulnerability. But it's now up to date (2.8.0).

By the way, you can use asdf-vm with flutter plugin or https://fvm.app to install latest flutter without delays

just a heads up 2.8 is released now

why this is not updated yet?

/opt/flutter/bin/internal/shared.sh: line 229: /opt/flutter/bin/cache/dart-sdk/bin/dart: No such file or directory

i'm peacefully using flutter! but after few days of break this error comes up!

they put Dart in the Flutter archive for some reason

Yes, the reason is that breaking changes to the Dart SDK are landed with the corresponding fixes to the Flutter SDK. Also, you cannot "remove it" without significantly altering the Flutter tooling. The Flutter CLI tool ensures that the pinned version of the Dart SDK is present in its binary cache.

If you want to use a version of Flutter without depending on Flutter's pinned version of the Dart SDK, you would need to maintain a separate fork of the Flutter SDK, that tracks the breaking changes of the Arch Dart package, and has an updated Flutter tool that doesn't assume it controls the Dart installation.

Yes it blows my mind, they put Dart in the Flutter archive for some reason. I think we can safely remove it from there and use the system Dart

Cannot we use dart package instead of downloaded dark sdk from flutter?