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 !

@yanpas I solved the conflicting files issue by running: paru -S --overwrite '*' flutter

Can't update to 3.0.3, get tons of errors like: flutter: '/opt/flutter/bin/cache/pkg/sky_engine/lib/ui/plugins.dart' file exists in a filesystem

@ricardosimoes i also got the same error and did the same to fix it. ^_^

@ricardosimoes I also encountered the same issue on Arch, did the same thing you did.

Got error: failed to commit transaction (conflicting files) flutter: /opt/flutter/.git/FETCH_HEAD exists in filesystem on MANJARO, but I ran sudo mv /opt/flutter/.git/FETCH_HEAD /opt/flutter/.git/FETCH_HEAD.bak and then it built fine

Solution to mkdir: cannot create directory ‘/opt/flutter/bin/cache’: Permission denied
You need to run the command to add your user to the group.
Run gpasswd -a <user> flutterusers

Not sure if this is an issue but flutter doctor started giving me this error:

fatal: unsafe repository ('/opt/flutter' is owned by someone else) To add an exception for this directory, call:

git config --global --add safe.directory /opt/flutter

Which is true because /opt/flutter is owned by root.

The solution mentioned in the error works though.

Running flutter doctor i get this error: Flutter failed to check for directory existence at "/root/.pub-cache/hosted/pub.dartlang.org/_fe_analyzer_shared-31.0.0/lib/". Please ensure that the SDK and/or project is installed in a location that has read/write permissions for the current user. Try running: sudo chown -R $(whoami) /root/.pub-cache/hosted/pub.dartlang.org/_fe_analyzer_shared-31.0.0

Any suggestion?

Hello

When I try to do this as a user (deps for another package):

flutter config --enable-web
mkdir: cannot create directory ‘/opt/flutter/bin/cache’: Permission denied

is it possible to change the cache directory somewhere else ?