I opened a PR to update this: https://github.com/frealgagu/archlinux.flutter/pull/9
Search Criteria
Package Details: flutter-gradle 3.22.1-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/flutter.git (read-only, click to copy) |
---|---|
Package Base: | flutter |
Description: | Flutter SDK component - gradle wrapper |
Upstream URL: | https://flutter.dev |
Keywords: | android fuchsia ios mobile sdk |
Licenses: | custom, BSD, CCPL |
Groups: | flutter |
Conflicts: | flutter-gradle, flutter-target-android |
Provides: | flutter-gradle |
Submitter: | flipflop97 |
Maintainer: | WithTheBraid |
Last Packager: | WithTheBraid |
Votes: | 134 |
Popularity: | 5.11 |
First Submitted: | 2017-06-05 21:03 (UTC) |
Last Updated: | 2024-05-28 08:55 (UTC) |
Dependencies (5)
- dart (flutterupAUR, fvm-flutter-proxyAUR, flutter-binAUR, flutter-dart-google-binAUR, dart-sdk-devAUR) (make)
- gradle (gradle7) (make)
- jq (jq-gitAUR) (make)
- unzip (unzip-natspecAUR, unzip-zstdAUR) (make)
Required by (1)
Sources (9)
Latest Comments
« First ‹ Previous 1 .. 13 14 15 16 17 18 19 20 21 22 23 24 Next › Last »
cfujino commented on 2021-06-17 17:15 (UTC)
SafwanLjd commented on 2021-05-05 08:35 (UTC) (edited on 2021-05-05 08:40 (UTC) by SafwanLjd)
This package was flagged out of date on the 4th of May for not releasing the 2.0.6 update; however, the 2.0.6 Flutter release was a hotfix for a bug on macOS and it doesn't concern GNU/Linux.
Form Flutter's official Github page:
2.0.6 (April 16, 2021)
This is a hotfix release that addresses a single issue:
• Issue #81326 - macOS binaries not codesigned There are no code changes to this release, but binary artifacts for macOS were re-built and codesigned.
cfujino commented on 2021-04-30 18:03 (UTC)
.git
is required by the CLI tool. The others aren't required, but if you mutate the checkout then the flutter upgrade
command won't work.
masterberg commented on 2021-04-30 16:57 (UTC)
Are the .git/
, .github/
, .idea/
folders really required? They are massive (over 135MiB) and seems to have no use at all. Shouldn't the PKGBUILD leave those out of the install process?
masterberg commented on 2021-04-28 18:20 (UTC)
I had the same problem as hossamdash and following his solution fixed it.
astroanax commented on 2021-02-27 08:55 (UTC)
I had the same problem as hossamdash and following his solution fixed it.
JuniorJPDJ commented on 2021-01-14 01:29 (UTC)
flutter-dev is now orphaned, didn't you think about taking it?
hossamdash commented on 2021-01-12 11:50 (UTC) (edited on 2021-01-12 11:53 (UTC) by hossamdash)
so i have installed this package but was facing two issues: Although i had the dart package installed on my system -which this package depends on-, both installing this package for the first time and each flutter doctor -v
command results in the redownload of the dark-sdk which is inside /opt/flutter/bin/cache disregarding both the existing dark-sdk in the cache and the standalone dart package installed on my system. to solve this i did two things, i uninstalled the standalone dart sdk and then added a line to the build files of this package right after the chmod -R g+w /opt/flutter
line.
this line is chmod g+s /opt/flutter
makes any files created within the /opt/flutter path inherit the group flutterusers which stops flutter doctor from redownloading the dart-sdk.
francescortiz commented on 2020-12-31 10:06 (UTC)
I think that flutter is designed to be self-upgraded. Hence in the end I decided to clone flutter repo instead of using AUR.
midhun commented on 2020-12-31 03:22 (UTC)
Getting failed to commit transaction error.
Using the --overwrite /opt/flutter/packages/flutter_tools/.packages
option solves the issue, but the question is, is it fine to overwrite?
Pinned Comments
WithTheBraid commented on 2024-03-28 00:44 (UTC) (edited on 2024-05-10 11:44 (UTC) by WithTheBraid)
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
andaur/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
. Sadlyaur/paru
does not reach at building updates for the package without additional flags. Please useparu -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 executepacman -R flutter && pacman -Rns flutter
to clean up the previous installation of both package bases.If you build both package bases using
makepkg -sfC
and later on install all build outputs usingpacman -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.
WithTheBraid commented on 2024-03-25 20:55 (UTC) (edited on 2024-05-10 11:45 (UTC) by WithTheBraid)
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 packagesflutter-common
: the common files for Flutter needed for all use casesflutter-devel
: your option of choice as a developer - ships the Flutter tool and all required templates to e.g. create a new projectflutter-tool
: The pure Flutter tool. Use asdepends
to build your package.flutter-target-linux
: The Flutter Linux build files. Use asdepends
to build your package.flutter-target-web
: The Flutter web build files. Use asdepends
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 theextra/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 !