Open PolarianDev opened 1 year ago
@PolarianDev close this issue
Shortly, I am still waiting on the finalisation.
@adil192 I can not update the package to the version you pushed today because flutter is broken, without any response from the devs or the package maintainers for arch.
Currently when flutter is outdated the tool self destructs, so unfortunately I can't build saber until then.
Just a quick note, I have not forgot about this package but currently have other priorities.
If you have experience with Arch Linux package maintaining, I am happy to give you co-maintainer so you can also help keep saber up to date.
However as I have explained on the wiki, the saber package is flaky due to the bad flutter support on Arch Linux.
The latest version pushed today (v0.15.2
) has been built successfully, I have pushed it to the AUR.
Enjoy!
Hello,
It has happened again, yet again flutter
has been updated, and the google team messed up the update and overwrote another version meaning that flutter
is broken until the next flutter update, I attempted to update saber but I can't compile it because flutter
is broken:
https://git.polarian.dev/AUR/saber/pulls/6#issuecomment-217
I will reattempt building saber once flutter is updated.
I apologise for the constant pain of dealing with awful flutter support, I am trying my best.
The flatpak or appimage can be used in the meantime.
Take care, Polarian
Latest flutter version has worked within Arch Linux, v.0.15.5
has now been pushed to the AUR and is available prebuilt on polarrepo
.
Man dealing with flutter is a right pain, but hey the latest version of saber is working natively again \o/
Latest version (0.17.0
) has been pushed to the AUR and polarrepo
.
However when building this I saw the following:
! bson 4.1.0 from git https://github.com/adil192/bson at a176e3 (overridden)
collection 1.17.2 (1.18.0 available)
csv 5.0.2 (5.1.0 available)
dynamic_color 1.6.7 (1.6.8 available)
file 6.1.4 (7.0.0 available)
flutter_keyboard_visibility 5.4.3 (retracted)
flutter_lints 2.0.3 (3.0.0 available)
flutter_quill 7.4.7 (7.8.0 available)
go_router 11.1.4 (12.0.0 available)
irondash_engine_context 0.3.1 (0.4.0 available)
! json2yaml 3.0.1 from git https://github.com/adil192/json2yaml at 618fc6 (overridden)
lints 2.1.1 (3.0.0 available)
material_color_utilities 0.5.0 (0.8.0 available)
meta 1.9.1 (1.11.0 available)
! pdf 3.10.5 from git https://github.com/DavBfr/dart_pdf at 41cbf8 in pdf (overridden)
! perfect_freehand 1.0.4 from git https://github.com/adil192/perfect-freehand-dart at f26bc5 (overridden)
petitparser 5.4.0 (6.0.1 available)
platform 3.1.0 (3.1.3 available)
! printing 5.11.1 from git https://github.com/DavBfr/dart_pdf at 41cbf8 in printing (overridden)
process 4.2.4 (5.0.1 available)
process_run 0.13.1 (0.13.2 available)
stack_trace 1.11.0 (1.11.1 available)
stream_channel 2.1.1 (2.1.2 available)
super_clipboard 0.6.4 (0.7.0 available)
super_native_extensions 0.6.4 (0.7.0 available)
test_api 0.6.0 (0.6.1 available)
uuid 3.0.7 (4.1.0 available)
vm_service 11.7.1 (12.0.0 available)
web 0.1.4-beta (0.3.0 available)
webdriver 3.0.2 (3.0.3 available)
xml 6.3.0 (6.4.2 available)
Seems a lot of the dependencies are outdated @adil192 , I doubt this matters too much, just a small heads up.
Take care, Polarian
This is normal don't worry
Hello world,
So I found saber via fdroid because it bumps recently updated, or added apps to the top of the store. I also realise that the app is not contained in any official arch repository, nor the AUR, so I intended to package it.
The reason I am making an issue to inform you of this is because I believe in communication between a package maintainer and upstream to ensure the highest quality builds possible.
I would be submitting saber to the AUR today, however due to dependency issues this can not be done.
Flutter is within the AUR, but the package is disfunctional and refuses to build any flutter application, due to the fact it constantly tries to connect to google servers, and pull stuff down which is not possible. Therefore, I must write up one (or more) patches to flutter before I can even build saber.
I do notice you provide an Appimage for Linux, I can use this to create a
-bin
package, but these are generally avoided for the sake of security and privacy, as nobody is able to verify the code compiled is not malicious when its in binary form, which is why source builds are preferred.So for
saber-bin
I can most likely submit that by the end of the day, the appimage should contain a natively built executable.If the package is voted, and popular, and a official package maintainer (Formerly TU) is willing to take the package on, it will be moved into the official repository where anyone can pull it directly through the use of
pacman
.Have a good day, Polarian