New package: flutter-3.7.11

[Bnyro]

Testing the changes

• I tested the changes in this PR: YES

New package

• This new package conforms to the package requirements: YES

Local build testing

• I built this PR locally for my native architecture, (x86_64)

as per #12749

Currently, it's still required to run chmod -R {username}:{username} /opt/flutter in order for flutter to work properly, I'd be happy to get an advice how to handle this inside the template.

[Chocimier]

chown {username}

Void is multi-user OS, so if /opt/ need to be owned to be useful, this not packagable.

[triallax]

Would this fit in better as a restricted package? It essentially just redistributes the Flutter tarball.

[paper42]

Would this fit in better as a restricted package? It essentially just redistributes the Flutter tarball.

I think it should be nonfree because we are not building from source. Afaik restricted is usually used for packages we can not distribute, is it this case?

Either way, building from source would be much better, we could build for multiple architectures, modify the source when needed and remove the nonfree restriction. This way it's equivalent to 2 commands - curl and tar xf

[Bnyro]

Either way, building from source would be much better, we could build for multiple architectures, modify the source when needed and remove the nonfree restriction. This way it's equivalent to 2 commands - curl and tar xf

Yes, I agree on that. I've been looking into the documentation on how to build flutter from source, however I doubt I'll be able to get that working given my few experience on building and packaging. I assume the best thing would be to close this PR and wait for somebody else to take the efforts to build it from source?

[triallax]

I think it should be nonfree because we are not building from source. Afaik restricted is usually used for packages we can not distribute, is it this case?

Yeah, I didn't consider that, I guess this might better fit in in nonfree.

Either way, building from source would be much better, we could build for multiple architectures, modify the source when needed and remove the nonfree restriction. This way it's equivalent to 2 commands - curl and tar xf

I agree, but this is the best we can do until somebody comes up with a template to build Flutter from source.

[triallax]

An update, somebody pointed me to this recently:

There seems to be some work over at Alpine Linux to package Flutter from source: https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/44347

Predictably, it doesn't look trivial at all.

Originally posted by @mhmdanas in #12749 (comment)