(Question) Possibility/interest of making Cromite available on package managers, like Scoop.sh?

[Spacellary]

Either Scoop, Chocolatey or Winget really, just wondering if it'd be something of interest?

Specially Scoop.sh has always been by go to portable installations and other utilities, but I am positive any other package manager solution for PC would be more than enough.

Cheers and thanks for the great project so far!

Sorry for the blank issue.

Checked:
[ X ] README
[ X ] FAQ
[ X ] ISSUES

[uazo]

Either Scoop, Chocolatey or Winget really, just wondering if it'd be something of interest?

Currently, personally, I use chrlauncher (look https://github.com/uazo/bromite-buildtools#test-windows-version) because I don't like the installers, too opaque.
chrlauncher, however, does not allow me to run post-installation scripts, which would allow me to launch e.g.
uazo/bromite-buildtools#51 (comment) required to activate the network process sandbox
would one of these allow me to do so?

[Spacellary]

From what I can gather from their documentations, both Chocolatey (https://docs.chocolatey.org/en-us/features/hook – entire installation process is scriptable) and Scoop (https://github.com/ScoopInstaller/Scoop/wiki/App-Manifests – pre/post_install scripts) offer full control and the possibility of running pre/post install scripts/commands.

[uazo]

uazo/bromite-buildtools#51 to be verified for https://github.com/uazo/cromite#enable-network-process-sandbox-in-windows

[uazo]

scoop seems like too much work, from what I understand every time I make a release I should make a pull request and wait for their OK. unless I enter their bucket main, where there are fewer pulls, but I do not have the prerequisites

Chocolatey is also pay-as-you-go, so I don't care
winget requires an installer and I don't like them

I leave the issue open for those who want to try, but I will not.

[opusforlife2]

@uazo Is it okay if I open a request for packaging Cromite in Chocolatey? Do you think Cromite is stable and ready for Windows distribution? Or is it still experimental?

[ContinuumOperand]

@opusforlife2 I am under the impression that chocolatey would be even worse than scoop to maintain given how frequently Cromite is updated, unless it's not?

[opusforlife2]

Packages are updated by bots, regardless of who decides to take up maintainership. Problems only arise when changes occur to the software that need code changes in the Chocolatey package installer or updater scripts. Otherwise it's just a matter of a bot updating the latest package URL.

[uazo]

Is it okay if I open a request for packaging Cromite in Chocolatey?

I don't see what's wrong with that.
just keep me updated please

Or is it still experimental?

it depends on what you mean. for me, this project will always be a forge of experiments.

[opusforlife2]

@uazo If someone does volunteer as a maintainer, you could interact with them to see if your intended post install hardening is something that could be incorporated in the package. Or you could let them do a standard install and see how it fares.

I brought up Chocolatey because you've said chrlauncher doesn't allow post-install tweaking.

---

What I mean is, is it okay for a lay user to install Bromite for Windows and let it be updated without a care? Without having to keep tabs on bugs, etc. in this repo? Like the chromium variants on Woolyss? If that is the case, many people would be happy sticking to chrlauncher as well.

[uazo]

If someone does volunteer as a maintainer, you could interact with them to see if your intended post install hardening is something that could be incorporated in the package

I meant that with 'keep me updated'.
I am available here, I will answer, if I am able.

What I mean is, is it okay for a lay user to install Cromite for Windows and let it be updated without a care?

is obviously a user choice, I don't see how I could force the contrary (or maybe I don't understand what you mean).

[opusforlife2]

Okay let me put it this way: is Cromite for Windows as stable as Cromite for Android?

[uazo]

in my opinion yes.
in addition, the windows version is the one I use the most and is therefore the one most directly verified by me.

[opusforlife2]

Wait a second. I was in the process of opening a packaging request and noticed that Cromite claims to be able to auto-update. If this is the case, then what is the need for a package manager at all? A user can simply download the chrome-win.zip once, and then let Cromite be auto-updated. Just like how a user would install regular Chrome or Firefox with auto-updates.

The reason I was talking of the Chocolatey package was because you said chrlauncher was an inferior solution, and I'm used to Chromium variants from Woolyss that can't auto-update and need an external update solution. Cromite is the first variant I've come across that talks about auto-updates.

Edit: BTW have you considered adding Cromite to Woolyss? It gets a lot of traffic from privacy-oriented people.

[opusforlife2]

@uazo ?

[uazo]

I was in the process of opening a packaging request and noticed that Cromite claims to be able to auto-update.

currently that feature is only active in android

[opusforlife2]

Thanks for clarifying. Do you have any tentative plans for Windows then? If no short or medium term plans for this exist, then it might be worth it to go ahead with Chocolatey.

Edit: @uazo Ping.

[kreml-rumatschov]

Hello, I have not much of sense to say, but user crisipa has added a manifest to their scoop bucket which allows for easy installation of Cromite with scoop. Can be found here: https://github.com/crisipa/scoopbucket/blob/master/bucket/cromite.json

For anyone else looking for package manager solution, hope this can help you save time

[ponces]

Hey everyone!

I have just added Cromite to the Chocolatey community repo at https://community.chocolatey.org/packages/cromite.
I have followed this tutorial to create the install script.

As it's still pending approval, for now you should be able to test this by downloading the nupkg file in the Chooclatey link above and installing it by running choco install cromite --source . in the folder where the nupkg is located.

My repo has a github workflow which should be able to detect everytime there's an update on the official repo. Nevertheless, if I understood correctly, chrlauncher has already this feature everytime it is called to open Cromite.

@uazo hope I'm following the rules and giving you all credit to you on the choco metadata file, poiting also to your license as it should be.

[opusforlife2]

Thanks for taking up maintainership of the chocolatey package! Now I can finally keep Cromite permanently on my PC.

[ponces]

Hey everyone!

I have just added Cromite to the Chocolatey community repo at https://community.chocolatey.org/packages/cromite. I have followed this tutorial to create the install script.

As it's still pending approval, for now you should be able to test this by downloading the nupkg file in the Chooclatey link above and installing it by running choco install cromite --source . in the folder where the nupkg is located.

My repo has a github workflow which should be able to detect everytime there's an update on the official repo. Nevertheless, if I understood correctly, chrlauncher has already this feature everytime it is called to open Cromite.

@uazo hope I'm following the rules and giving you all credit to you on the choco metadata file, poiting also to your license as it should be.

Cromite v126.0.6478.186 is already live!
v127.0.6533.73 is in approval state, should be live soon too :)

[uazo]

Carmelo Messina

please, use uazo :)

[ponces]

You mean on the package metadata?

[uazo]

everywhere, if you can

[ponces]

Got it! We'll update accordingly :)

[opusforlife2]

Wait a second. @ponces I just installed the Cromite package for testing. Turns out it's just a wrapper around the chrlauncher version. Wasn't the intention to allow scripting for hardening purposes? #108 (comment)

[ponces]

Yeah sure, I can add that call to the choco install script!

Just to clarify, as stated in my previous comment I followed the tutorial to create these scripts.
In fact, chrlauncher doesn't make sense to use as choco handles updates so it was removed.

Next release should include both of these changes :)

[opusforlife2]

Awesome! The package is finally a trusted package, so users won't have to wait for mod approval for weeks to get security updates now.

Now to install it and discover all the bugs. Mwahaha.

[opusforlife2]

@ponces With chrlauncher, it is possible to specify (and is there by default) that the profile directory should be in the same folder as Cromite. Is it possible to have the Choco package do the same? Or with a Portable variant of it?

Having browser data in one place makes it easy to back up and restore it in case of problems.

[ponces]

I could add an argument to specify a path but by default I would rather prefer the usual behavior...