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 !

@xeruf execute git config --global --add safe.directory /opt/flutter

OR add this lines to .gitconfig file

[safe]
    directory = /opt/flutter

After adding my user to flutterusers, I still get this:

❯ flutter doctor
fatal: detected dubious ownership in repository at '/opt/flutter'
To add an exception for this directory, call:

    git config --global --add safe.directory /opt/flutter
Doctor summary (to see all details, run flutter doctor -v):
Failed to find the latest git commit date: VersionCheckError: Command exited with code 128: git -c
log.showSignature=false log HEAD -n 1 --pretty=format:%ad --date=iso
Standard out: 
Standard error: fatal: detected dubious ownership in repository at '/opt/flutter'
To add an exception for this directory, call:

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

Returning 1970-01-01 01:00:00.000 instead.
[!] Flutter (Channel unknown, 0.0.0-unknown, on Arch Linux 6.0.8-arch1-1, locale en_IE.UTF-8)
    ! Flutter version 0.0.0-unknown on channel unknown at /opt/flutter
    ! Upstream repository unknown

After installation I get this confusing error:

❯ flutter run .
fatal: detected dubious ownership in repository at '/opt/flutter'
To add an exception for this directory, call:

    git config --global --add safe.directory /opt/flutter
rm: cannot remove '/opt/flutter/version': Permission denied

This doesn't actually build anything. Either the name should be updated to -bin or this package should be corrected.

See this and this for compilation steps.

Also if you're going to the effort of messing with permissions, you might as well go all the way; for find "${pkgdir}/opt/${pkgname}" -type d -exec chmod a+rx {} + you can change a+rx to a+rx,g+w, since it will avoid noisy warnings during update of this package and will align with the whole purpose of creating the flutterusers group.

And as has been said before, when bumping pkgver then pkgrel should be reset to 1.

u should reset pkgrel to 1 if you update pkgver https://wiki.archlinux.org/title/PKGBUILD#pkgrel

Flutter failed to create a directory at "/opt/flutter/bin/cache/downloads".

@orzogc Adding to flutterusers doesn't help. EDIT: Nevermind. Had to logout and login back again.

please update pkgrel=1

The terminal-gymnastics in the flutter.install script won't work properly in non-terminal environments (e.g. in Pamac):

tput: No value for $TERM and no -T specified
tput: No value for $TERM and no -T specified
tput: No value for $TERM and no -T specified
Flutter was installed on /opt/flutter
tput: No value for $TERM and no -T specified
tput: No value for $TERM and no -T specified

tput: No value for $TERM and no -T specified
tput: No value for $TERM and no -T specified
In case you encounter problems using Flutter as regular user, add your user into the group flutterusers:
tput: No value for $TERM and no -T specified
tput: No value for $TERM and no -T specified
gpasswd -a ${USER} flutterusers
tput: No value for $TERM and no -T specified
tput: No value for $TERM and no -T specified

tput: No value for $TERM and no -T specified
tput: No value for $TERM and no -T specified
Re-login your terminal in to the group flutterusers:
tput: No value for $TERM and no -T specified
tput: No value for $TERM and no -T specified
newgrp flutterusers
tput: No value for $TERM and no -T specified
tput: No value for $TERM and no -T specified

tput: No value for $TERM and no -T specified
tput: No value for $TERM and no -T specified
Run the following command to see if there are any dependencies you need to install to complete the setup (for verbose output, add the -v flag):
tput: No value for $TERM and no -T specified
tput: No value for $TERM and no -T specified
flutter doctor

@Gigas002 Add your user to the flutterusers group.

Got the following error on flutter doctor command:

Flutter failed to create a directory at "/opt/flutter/bin/cache/downloads".
Please ensure that the SDK and/or project is installed in a location that has read/write permissions for the current user.