This merge request would leave AUR without a working stable flutter package. The requester [a] is the maintainer of `flutter` [b] and associated packages [c]. A couple months ago, he split `flutter` into numerous dysfunctional subpackages across multiple pkgbases. They typically work for a short period after being updated, but quickly go out of sync and stop working (usually within days). Evidence of this may be seen in numerous commments complaining about the package.
`flutter-bin` [d] is needed to provide users with a working flutter. It has to provide and conflict with all `flutter`-associated to capture the depends. Having provides/conflicts with only flutter is insufficient because the maintainer of `flutter` has encouraged other packages to depend on subpackages. At the time of its creation, `flutter-bin` was tested and confirmed to satisfy flutter-related build depends, except for `flutter` itself. Whether `flutter-bin` continues functioning in this capacity depends on how the other packages are maintained, and is not a valid reason for deletion or merge. This package, like most AUR package, does not affect other packages on systems that do not have it installed. While a user did mistakenly attempt to use `flutter-bin` to build `flutter`, the conflicts correctly prevented them from co-installing conflicting packages. This is the packaging working as intended, not "breaking" anything. The scenario can be prevented by updating the pinned install instructions at `flutter` to inform users that `flutter-bin` is incompatible with the 17 `flutter`-associated subpackages. [a]: https://aur.archlinux.org/account/WithTheBraid [b]: https://aur.archlinux.org/pkgbase/flutter [c]: https://aur.archlinux.org/pkgbase/flutter-artifacts-google-bin [d]: https://aur.archlinux.org/pkgbase/flutter-bin
