Do you know where it stores files? BleachBit version 1.17 recognizes only ~/.config/google-chrome/. If it is elsewhere, you can edit or clone BleachBit's google_chrome.xml
where is this file located ?google_chrome.xml , i can see its in google_chrome.xmlsource code, but after the installation where does this file resides ??
Location of file in typical installation: /usr/share/bleachbit/cleaners/google_chrome.xml
Which lines to change: all lines with /google-chrome/
If you want to support both stable and beta versions of Google Chrome
1. Copy google_chrome.xml to google_chrome_beta.xml in the same directory
2. Do a search and replace (using vim or sed or whatever) for /google-chrome/
3. Change id="google_chrome" to id="google_chrome_beta"
4. The LABEL tag on the next line
5. Save the file
andrew
Wed, 07/05/2017 - 21:44
Permalink
Do you know where it stores
Do you know where it stores files? BleachBit version 1.17 recognizes only ~/.config/google-chrome/. If it is elsewhere, you can edit or clone BleachBit's google_chrome.xml
---
Andrew, lead developer
narutowindy
Wed, 07/05/2017 - 22:31
Permalink
inside google_chrome.xml ,
inside google_chrome.xml , which lines are to change ?? can i use vim for replace "%s/google-chrome/googlel-chrome-unstable/g"
narutowindy
Wed, 07/05/2017 - 22:33
Permalink
where is this file located
where is this file located ?google_chrome.xml , i can see its in google_chrome.xmlsource code, but after the installation where does this file resides ??
andrew
Thu, 07/06/2017 - 20:53
Permalink
Location of file in typical
Location of file in typical installation: /usr/share/bleachbit/cleaners/google_chrome.xml
Which lines to change: all lines with /google-chrome/
If you want to support both stable and beta versions of Google Chrome
1. Copy google_chrome.xml to google_chrome_beta.xml in the same directory
2. Do a search and replace (using vim or sed or whatever) for /google-chrome/
3. Change id="google_chrome" to id="google_chrome_beta"
4. The LABEL tag on the next line
5. Save the file
---
Andrew, lead developer