Skip to content
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

Closed
death-owl opened this issue Apr 19, 2020 · 10 comments
Closed

Auto-delete of old Chromium versions? #180

death-owl opened this issue Apr 19, 2020 · 10 comments
Labels

Comments

@death-owl
Copy link

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

@woolyss
Copy link

woolyss commented Apr 25, 2020

should it auto-delete the old version(s)?

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:

  • like ChromiumRemoveOldVersions=true
  • or like ChromiumMaxOldVersions=2 --> It means only the 2 latest versions will be kept. "0" means no old versions.

@syndenbock
Copy link

I don't think the behaviour comes from chrlauncher itself, as when using ungoogled-chromium, the structure in the "bin" folder is completely different.
I think the application simply downloads the archive from github and unpacks it in the "bin" folder, without emptying the folder beforehand. The "old versions" come from the structure of the release archives of this repo.
So an option to remove the old version beforehand would be great, but an option to keep specific versions is propably not as easily realizable.

@sirjeannot
Copy link

there must be some logic known to chrlaucher as it has knowledge as where the current bin is located to start it.

@syndenbock
Copy link

I'm pretty sure it just statifcally launches "./bin/chrome.exe".

@henrypp
Copy link
Owner

henrypp commented Jan 14, 2021

chrlauncher always cleanup .\bin folder before installation, you have use old version of chrlauncher.

@syndenbock
Copy link

I'm using version 2.5.7 which is the latest release listed on github.

@death-owl
Copy link
Author

I've also been using 2.5.7.

@henrypp henrypp added bug and removed question labels Jan 16, 2021
@henrypp
Copy link
Owner

henrypp commented Jan 16, 2021

Yes, this is bug. I fix this soon.

@syndenbock
Copy link

Thank you very much for your great work!

@AdKiller
Copy link

AdKiller commented Apr 1, 2021

I was about to post the same question. today I noticed 2 GB of old versions in ChromiumPortable\bin folder.

@henrypp henrypp closed this as completed Jan 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

6 participants