You would add it to this line here: rpm -U -nodeps -prefix=/opt google-chrome*.rpm Anyway that is actually already a good example of using native curl without bothering to define a repo for dnf. Many of my zsh scripts use google with chrome to grab documents and resources. And the line sudo tee -a /etc/profile.d/fonts.sh <<'EOF'Įxport FONTCONFIG_PATH=/usr/share/defaults/fonts

The only immediate change I make is to add -prefix=/opt to put it in a little better location. I may make a few changes later, but that is a good quick way to just go and quickly get it. It comes up first in a google search and when I’m in a hurry I need chrome fast, because I use chrome to speed up other workflows. process outlined above by UbitoUchiha, also process utilizing rpm2cpio and process published by Mattia Verticchio in Clear Linux Tutorials?Īctually, TBH on new systems I use MattiaVerticchio’s example for chrome when I’m in a hurry and in the wild with no other tools onhand (and can’t remember the download url). How would your approach to install rpm compare line by line taking one common example of installing chrome, vs.

The above steps will help us to keep track of updates, so that we won’t have to visit their websites to get rpms every week, or to check for updates.

There are many steps to do so, even better ones. Recently I found that a new version of vs code released, but dnf check-update was unable to sync that. If new updates available we can repeat above steps Now we can keep track of updates just with a single command …> sudo sh -c ‘echo -e “ name=Visual Studio Code baseurl= enabled=1 gpgcheck=1 gpgkey=” > /etc//vscode.repo’

Yum install rpm file