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 !

@WithTheBraid I keep getting the same error "Null check operator used on a null value". Does anyone know of an alternative to installing flutter while this (broken) package is being fixed?

After installing the new package I am getting this error:

An exception occurred applying plugin request [id: 'dev.flutter.flutter-gradle-plugin']
> Failed to apply plugin 'dev.flutter.flutter-gradle-plugin'.
   > /usr/lib/flutter/bin/internal/engine.version (No such file or directory)

I also cannot find the file anywhere anymore. It used to be there with the old version. Does anyone know what package I am missing or where the file might end up?

Anyone knows why i get this error even though I can search and even build the packages it says are not satisfied? I am using pamac by the way

EDIT: I ended up building it by installing all the dependencies first

Error: Failed to prepare transaction:
could not satisfy dependencies:
- unable to satisfy dependency 'flutter-engine-android' required by flutter-target-android
- unable to satisfy dependency 'flutter-engine-linux=3.19.4' required by flutter-target-linux
- unable to satisfy dependency 'flutter-target-linux=3.19.4' required by flutter
- unable to satisfy dependency 'flutter-target-android=3.19.4' required by flutter
- unable to satisfy dependency 'flutter-engine-web=3.19.4' required by flutter-target-web
- unable to satisfy dependency 'flutter-target-web=3.19.4' required by flutter

@stelbl The dependencies are sadly due to the way Flutter is concepted. The flow is to install :

1. flutter-common

2. then installer flutter-material-fonts and flutter-sky-engine

3. flutter-engine-common

4. flutter-engine-*, flutter-gradle, flutter-tool

5. flutter-devel, flutter-target-*, flutter-intellij-patch

6. flutter

packages and then to install all remaining packages of the flutter package.

In case you use an aur helper, ensure that one can properly resolve between these subpackages. E.g. yay reaches there, though it's sadly very slow (it keeps repackaging the package dozens of times).

So I just tried to update but I've been getting these no matter what I do (tried both with flutter and aur/flutter);

resolving dependencies...
warning: cannot resolve "flutter-engine-linux=3.19.4", a dependency of "flutter-target-linux"
warning: cannot resolve "flutter-engine-web=3.19.4", a dependency of "flutter-target-web"
:: The following packages cannot be upgraded due to unresolvable dependencies:
      flutter-target-linux  flutter-target-web

:: Do you want to skip the above packages for this upgrade? [y/N] 

What's even weirder is that explicitly trying to install flutter-engine-{web,linux} installs flutter-engine-{linux,web}-google-bin. I guess some dependency declarations of flutter-target-{web,linux} need to be updated?

@WithTheBraid Still getting the same "Null check operator used on a null value" error with the updated packages.

Hello again, I have tried to install the package in three ways: using the package manager (GUI), cloning and doing makepkg -sifC and using trizen (the last one is the one I use in most cases, it always works well for me). In all three cases the same error results that I have been reporting.

Please, group all flutter packages into one single group called flutter, so we can uninstall easily with one command like sudo pacman -Rns flutter...

Getting the same circular dependency error if I try to install flutter (yay -S flutter), but aur/flutter installs fine.