-
-
Notifications
You must be signed in to change notification settings - Fork 76
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
Auto-delete of old Chromium versions? #180
Comments
No. As you know, you see the old Chromium versions in the "bin" folder. If think @henrypp can easy add an option to remove automatically old Chromium versions via a parameter in the .ini file. This is his choice 😉 Ideas:
|
I don't think the behaviour comes from chrlauncher itself, as when using ungoogled-chromium, the structure in the "bin" folder is completely different. |
there must be some logic known to chrlaucher as it has knowledge as where the current bin is located to start it. |
I'm pretty sure it just statifcally launches "./bin/chrome.exe". |
chrlauncher always cleanup .\bin folder before installation, you have use old version of chrlauncher. |
I'm using version 2.5.7 which is the latest release listed on github. |
I've also been using 2.5.7. |
Yes, this is bug. I fix this soon. |
Thank you very much for your great work! |
I was about to post the same question. today I noticed 2 GB of old versions in ChromiumPortable\bin folder. |
Hello. I recently started using Chrlauncher and it seems like a very good program, so thanks for it.
There's just one issue I've noticed so far: When it updates Chromium, should it auto-delete the old version(s)? Or was there some option I missed?
So, after it updated my Chromium from 81.0.4044.92 to 81.0.4044.113, I had two Chromium folders in the bin folder: both 81.0.4044.92 and 81.0.4044.113, both around 180 megabytes, taking up twice the disk space they should. I deleted the older one manually.
I would prefer for it to clean up the old version when it installs the new one, or at least have an option in the ini file for it to do so.
Some of my settings in the ini file, in case this behavior depends on any of these:
ChromiumAutoDownload=false
ChromiumBringToFront=false
ChromiumWaitForDownloadEnd=false
ChromiumType=stable-codecs-sync
ChromiumCheckPeriod=2
The text was updated successfully, but these errors were encountered: