-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Huge installation using flatpak #82
Comments
Thanks for reporting. Indeed, the size of package is ridiculously huge. To address this problem, next Flatpak package (v4.4.0) will be split into 3 parts:
So the plan is to significantly reduce the size of base package. If it is still too big, you might try "tiny" package. You can download it from Releases page and install manually. Comparison of "regular" and "tiny" package is here. |
May be the base package should be the tiny as 600 MB still is a lot.
Please update (in the next release) that table in the readme with those 3 parts and tiny |
This is something worth to consider. Initially, I did not want to create too many add-ons so as not to confuse the user.
Sure, I will do that. |
May be its more relevant to break it if every version would trigger flatpak to download the whole package.
----------------------------------------
Dec 30, 2023 16:04:09 mkiol ***@***.***>:
…
May be the base package should be the tiny as 600 MB still is a lot.
This is something worth to consider. Initially, I did not want to create too many add-ons so as not to confuse the user.
Please update (in the next release) that table in the readme with those 3 parts and tiny
Sure, I will do that.
—
Reply to this email directly, view it on GitHub[#82 (comment)], or unsubscribe[https://github.com/notifications/unsubscribe-auth/AKBEQUUUPTVUVHQYT3EDEMLYMAUOTAVCNFSM6AAAAABBGLT3GSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZSGU2DINJQG4].
You are receiving this because you authored the thread.
[Tracking image][https://github.com/notifications/beacon/AKBEQUUI5J44JEUCYHJGC4LYMAUOTA5CNFSM6AAAAABBGLT3GSWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTTPTTBPW.gif]
|
"Modular" version has been released 🎉 It looks like this (section from README): Starting from v4.4.0, the app distributed via Flatpak (published on Flathub) consists of the following packages:
Comparison between Base, Tiny and Add-ons Flatpak packages:
|
|
Unfortunately no. Right now GPU acceleration is only for selected models and only NVIDIA and AMD. In theory, Intel GPU is supported in whisper.cpp ("Whisper" models in Speech Note), but I didn't figure out how to make it work together with Flatpak package. Other STT models (e.g. "Faster Whisper") and all TTS models don't support Intel GPU acceleration at all.
Add-ons are separate packages, so any update to the "Base" will not require an update to the Add-ons. |
I meant that the base package is around 900 MB, does the next update of the base package would download the entire base package again or just the delta of the change? |
I think the entire package has to be downloaded after updating. I might be mistaken, but Flatpak/Flathub does not support "delta" updates or anything similar. |
May I suggest to offer the Tiny package as a flatpak and let user install the additional features TTS and STT from separate flatpak package(s). So when update happens to one flatpak package, the user just download that part. |
Good suggestion. The main problem is in Python dependencies. One small pip package needs a lot of other stuff. Moreover, there is no simply way to split them because in "python world" everything depends on everything. My pragmatic approach was "Tiny". "Tiny" is de facto "Base" without everything that depends on Python. This was the easiest way to downsize. I'm thinking about moving all Python dependencies to new add-on, so "Tiny" would become "Base". This might work 🤔 On the other hand, I don't want to make too many add-ons to not confuse users too much... |
May be its possible to install python specific modules using pipx, and use it with tiny? |
This might work but... To use anything outside Flatpak sandbox, you (as an advanced user) need to override permissions and grand access to specific directory where these manually installed Python libraries are located. I will think about it :) |
@mkiol If you have tried this, would be useful for beginners if you could provide the installation steps with pipx and tiny (flatpak), may be flatseal can be used for permission management. |
Installed using flatpak. It downloaded about 3 GB of data! Will each version update would download 3 GB every time? Also, is so much of data entirely necessary, for example I don't have any GPU except the in-built GPU (Intel), I am not sure why the software download is so huge? This does not include the language models that needs to be downloaded separately.
The text was updated successfully, but these errors were encountered: