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 !

@kronaemmanuel I bet that's because of https://github.com/flutter/flutter/issues/55082. Because of an infra change I made, the stable package got regenerated today, and I wouldn't be surprised if the checksum of the archive changed.

I'm getting this error. Any ideas on what I can try?

==> Validating source files with sha256sums...
    flutter-1.12.13+hotfix.9.tar.xz ... FAILED
    flutter.sh ... Passed
    flutter.csh ... Passed

sudo setfacl -m u:YOURUSERNAME:rwx -R /opt/flutter/ can also solve some permission issues before the flutter fix https://github.com/flutter/flutter/issues/44526.

Writing here for if anyone faces the same issue, in my case everything worked except for the hotreload feature, so i had to do flutter version 1.16.3. Otherwise hotreload and hotrestart buttons were gray.

@TheAifam5 unfortunately, at this time, maintaining the .git directory is required for the flutter sdk to work. For example, running flutter doctor uses git to check the version. There is an outstanding github issue to fix this, to better support installation from package managers: https://github.com/flutter/flutter/issues/44526.

If you are REALLY concerned about the disk space, you can make your git repo a shallow clone, via:

git pull --depth 1
git gc --prune=all

That for me got my .git directory from 157mb to 95mb ¯_(ツ)_/

Why lib32-libglvnd is required?

@rockypra Thank you for the clarification. I wonder if that is needed, even the package sticks to the specific version, and AUR provides also other versions like beta and dev.

Flutter SDK works that way, unfortunately. They use git for version management even for the user local snapshot. If you're managing Flutter SDK on your own, you can change which channel of release you want to follow with flutter channel Channel switching is basically fetching from their github repo, doing the branch switching, and updates the local snapshot. That's why when you try to change the channel or doing an upgrade you can see a lot of git related process like pulling from the git repository and/or branch switching.

No way that this package contains .git.... just WHYYYY... is SO BLOATED