Arch Linux User Repository

I've created a package fvm-sourcebuild for those who want to build the engine from sources. It will cache build artifacts in the same place as flutter-engine (~/.cache/flutter-engine).

Do you want me to do the same with hacki, convertall and python-flet?

The other problem is that flutter apps tend to need specific version of the engine in my experience. Like this package need an older version than flutter package. I've had a lot of problems with other apps where I couldn't update the engine version. It would become hell to manage if whenever flutter is updated and break apps. I created flutter-engine to address these problems. Trying to do it the traditional "linux" way is going to be extremely problematic.

I can rename my packages, however I don't see how anything is official or personal until I see some official arch guidelines.

The problem with flutter-engine is it is basically a personal package. Although there is currently no flutter package guidelines, there are definite trends established in other guidelines.

This package should be rewritten to use flutter or fvm. If this package continues to use flutter-engine it should have some identifying suffix. The flutter packages now build from source, so avoiding binaries is not a valid reason to use a custom package.

@patlefort: I never said anything "didn't work". Anyway, I made my point, never said I wanted to discuss it and shared a PKGBUILD I wrote that I will use myself so that others can use it if they wish. Have a good evening.

Disclaimer: I'm not feeling well today, so forgive me for being a little short.

What doesn't work about flutter-engine? I can make corrections if there are problems.

@patlefort: I understand about wanting to avoid downloading precompiled binaries during build. However, none of the Flutter related AUR packages attempting to address this work reliably. I use FVM for my Flutter AUR packages because it works well and reduces the time I need to spend on maintaining them.

@patlefort: I understand about not wanting to avoid downloading precompiled binaries during build. However, none of the Flutter related AUR packages attempting to address this work reliably. I use FVM for my Flutter AUR packages because it works well and reduces the time I need to spend on maintaining them.

Flutter engine version 3.13.9, which localsend depends on, needs python 3.11 to compile. I don't think people understand how flutter work. By default it will download precompiled binaries from google, which I want to avoid. I don't see anything about compiling the engine from source in fvm. But if you still want that, you can use flutter-engine-google-bin package instead of flutter-engine.