Package Details: flutter-bin 3.29.3-1

Git Clone URL: https://aur.archlinux.org/flutter-bin.git (read-only, click to copy)
Package Base: flutter-bin
Description: Cross platform widget toolkit for Dart (monolithic)
Upstream URL: https://github.com/flutter/flutter
Licenses: BSD-3-Clause, LicenseRef-Google-Patent-Grant
Conflicts: dart, flutter, flutter-common, flutter-devel, flutter-engine, flutter-engine-android, flutter-engine-android-google-bin, flutter-engine-common, flutter-engine-common-google-bin, flutter-engine-linux, flutter-engine-linux-google-bin, flutter-engine-web, flutter-engine-web-google-bin, flutter-gradle, flutter-gradle-google-bin, flutter-intellij-patch, flutter-material-fonts, flutter-material-fonts-google-bin, flutter-sky-engine, flutter-sky-engine-google-bin, flutter-target-android, flutter-target-linux, flutter-target-web, flutter-tool, flutter-tool-developer
Provides: dart, flutter, flutter-target-android, flutter-target-linux, flutter-target-web, flutter-tool
Submitter: xiota
Maintainer: xiota
Last Packager: xiota
Votes: 5
Popularity: 0.083478
First Submitted: 2024-04-22 06:23 (UTC)
Last Updated: 2025-04-18 09:03 (UTC)

Required by (93)

Sources (1)

Pinned Comments

patlefort commented on 2024-07-11 10:23 (UTC)

Users can choose to use fvm-sourcebuild to build packages that use fvm, if they want to build flutter engine from source.

xiota commented on 2024-05-14 14:11 (UTC) (edited on 2024-05-14 14:12 (UTC) by xiota)

Packagers: Consider using aur/fvm.

xiota commented on 2024-04-22 06:49 (UTC) (edited on 2024-07-23 23:53 (UTC) by xiota)

aur/flutter-bin is needed to provide a working stable flutter package. It is intended to be installed by itself, without any other flutter or dart package.

The conflicts are needed to prevent co-installation with other flutter packages. The provides are needed to capture the build depends of packages that use flutter.

Flutter requires write permissions to its install directory, /opt/flutter. These may be provided by one of two methods:

  • By default, the executable scripts create a unionfs mirror at ~/.cache/flutter_*. Users should unmount and clear them after upgrades.

    fusermount -uq ~/.cache/flutter_sdk
rm -rf ~/.cache/{flutter_sdk,flutter_local}

  • Allow writing directly to the flutter install path by adding users to the flutter group. Do not store important files there because it is cleared at install and upgrade.

Latest Comments

1 2 Next › Last »

xiota commented on 2025-03-17 19:23 (UTC)

@Tech-Tac That doesn't solve the problem on the packaging side. Also, pacman/aur helper may still display warnings about the package being out of date.

Tech-Tac commented on 2025-03-17 18:58 (UTC) (edited on 2025-03-17 18:59 (UTC) by Tech-Tac)

@xiota I'm not really familiar with PKGBUILDs, but I think it is possible flag specific packages to prevent them from being marked as outdated in Pacman/yay by adding them to IgnorePkg, and then we can update using the flutter upgrade command instead.

xiota commented on 2025-03-17 18:23 (UTC)

@Tech-Tac Do you know of a solution?

Tech-Tac commented on 2025-03-17 13:34 (UTC)

This package is nice for installing Flutter, but not for updating it. Simply running flutter upgrade is more efficient than updating through this package as it only downloads the diffs and applies them directly, while this package has to re-download the whole archive again and extract, and then repackage it, and then extract it in the target location, leaving behind 3GBs of duplicate flutter tars. But updating Flutter with the upgrade command doesn't update the package version, making it appear as having available updates in yay and other.

xiota commented on 2025-03-16 09:36 (UTC)

@Erwin_Iosef On my computer, pacman reports compressed package size is 864.53 MiB, installed size is 1727.28 MiB. I'd prefer to leave compression settings alone because changing them could cause problems for some users.

Erwin_Iosef commented on 2025-03-16 08:40 (UTC)

@xiota thanks for the package, on compression using paru the pkg just gets reduced to a mere 700 MB compared to the 731 flutter.tar and takes a long time to compress. Maybe it'd be beneficial to disable compression for this pkgbuild?

patlefort commented on 2024-07-11 10:23 (UTC)

Users can choose to use fvm-sourcebuild to build packages that use fvm, if they want to build flutter engine from source.

xiota commented on 2024-07-07 04:05 (UTC) (edited on 2024-08-22 12:25 (UTC) by xiota)

@Dieter_be I'll consider your suggestions, but not going to make any changes now.

Updates:

  • Revised pinned comment for clarity.
  • Revised install messages for clarity.
  • Moved flutter_init out of /usr/bin
  • TBD

Dieter_be commented on 2024-07-06 20:16 (UTC)

@xiota perahps your wrappers and scripts should live in a separate repository, so they can be properly contributed on with issues and PR's. they also seem distribution agnostic

i believe /usr/bin is only meant for programs or scripts, your flutter_init is meant to be sourced and not executed, so it doesn't seem /usr/bin is appropriate for it.

there's quite a lot going on in your scripts and some comments in it would be quite helpful.

your approach to allow both unionfs OR direct-writeable /opt/flutter (via flutter group) is quite interesting. a note about this during package installation would probably be a helpful clarification. i don't think i a saw one.

xiota commented on 2024-07-06 16:26 (UTC) (edited on 2024-07-06 16:28 (UTC) by xiota)

@Dieter_be Flutter expects write permissions to the SDK directory. This is generally undesirable and causes problems for system-wide installs. The script allows flutter to write somewhere else (~/.cache/flutter_local). If you prefer to allow flutter to write to /opt/flutter, add your user to the flutter group. Set the SDK directory in other software manually.

1 2 Next › Last »