With -s I get exit code 2, but it gives me the files I'm looking for.
With -q I get exit code 0, but it doesn't give me the files I'm looking for.
Search Criteria
Package Details: google-chrome-beta 132.0.6834.46-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/google-chrome-beta.git (read-only, click to copy) |
---|---|
Package Base: | google-chrome-beta |
Description: | The popular web browser by Google (Beta Channel) |
Upstream URL: | https://www.google.com/chrome |
Keywords: | chromium |
Licenses: | custom:chrome |
Provides: | google-chrome |
Submitter: | None |
Maintainer: | gromit |
Last Packager: | gromit |
Votes: | 357 |
Popularity: | 0.66 |
First Submitted: | 2009-12-08 19:09 (UTC) |
Last Updated: | 2024-12-11 20:27 (UTC) |
Dependencies (12)
- alsa-lib
- gtk3 (gtk3-no_deadkeys_underlineAUR, gtk3-classicAUR, gtk3-classic-xfceAUR, gtk3-patched-filechooser-icon-viewAUR)
- libcups (libcups-gitAUR, cups-gitAUR, libcups-gssapiAUR)
- libxss
- libxtst
- nss (nss-hgAUR)
- ttf-liberation (ttf-defenestrationAUR)
- xdg-utils (busking-gitAUR, xdg-utils-slockAUR, mimiAUR, mimi-gitAUR, xdg-utils-handlrAUR, openerAUR, xdg-utils-mimeoAUR, mimejs-gitAUR)
- gnome-keyring (gnome-keyring-gitAUR) (optional) – for storing passwords in GNOME keyring
- kdialog (kdialog-gitAUR) (optional) – for file dialogs in KDE
- kwallet (kwallet-gitAUR) (optional) – for storing passwords in KWallet
- pipewire (pipewire-gitAUR, pipewire-full-gitAUR) (optional) – WebRTC desktop sharing under Wayland
Required by (42)
- bitwarden-chromium (requires google-chrome) (optional)
- captive-browser-git (requires google-chrome) (optional)
- chrome-extension-bitwarden-git (requires google-chrome) (optional)
- chrome-extension-ocrs-git (requires google-chrome)
- chromedriver (requires google-chrome) (optional)
- chromedriver-beta (optional)
- chromium-extension-adnauseam (requires google-chrome) (optional)
- chromium-extension-autoscroll (requires google-chrome) (optional)
- chromium-extension-plasma-integration (requires google-chrome) (optional)
- chromium-extension-runet-censorship-bypass (requires google-chrome) (optional)
- chromium-material-icons-for-github-bin (requires google-chrome) (optional)
- chromium-vencord (requires google-chrome) (optional)
- chromium-vencord-bin (requires google-chrome) (optional)
- chromium-vencord-git (requires google-chrome) (optional)
- dedao-dl-bin (requires google-chrome) (optional)
- endpoint-verification-chrome (requires google-chrome)
- endpoint-verification-minimal (requires google-chrome)
- ff2mpv-go-git (requires google-chrome) (optional)
- ff2mpv-rust (requires google-chrome) (optional)
- hub-kids (requires google-chrome) (optional)
- Show 22 more...
Sources (3)
Latest Comments
« First ‹ Previous 1 .. 19 20 21 22 23 24 25 26 27 Next › Last »
t3ddy commented on 2011-01-11 21:05 (UTC)
dhaines commented on 2011-01-11 20:39 (UTC)
I'm pretty sure that it should be either "-q" or "-qs" as "-s" doesn't change the exit status of the command, and thus wouldn't change the operation of the conditional. As an example: "echo string > realfile; ln -s fakefile brokenlink; grep -s string realfile brokenlink && echo success" prints realfile:string, but "echo string > realfile; ln -s fakefile brokenlink; grep -q string realfile brokenlink && echo success" prints (to stderr) grep: brokenlink: No such file or directory and (to stdout) success.
If you combine the two, you skip the error message and you get the right exit status.
t3ddy commented on 2011-01-11 20:27 (UTC)
Ah, ok.
Thanks for the explaination! :)
After some proof, the right flag should be -s, because -q neither tells the files.
dhaines commented on 2011-01-11 19:49 (UTC)
Because if there's a symlink to a nonexistent file in there, grep throws an error when it tries to read it. Skipping the conditional should work just fine.
t3ddy commented on 2011-01-11 19:44 (UTC)
mmm... I don't understand quite well.
With grep I'm searching in pkgdir, why should it be important if chrome has been already installed or not?
Anyway, I was planning to keep only this part: sed -i "s/google\/chrome/google-chrome/g" $(grep -Rl "/google/chrome" *)
and removing the "if-fi", since there's no reason to check if there are those kind of occurences, because they're present and I know that.
What do you think?
dhaines commented on 2011-01-11 19:06 (UTC)
The pkgbuild *almost* corrects this. Here's the skinny: the installation makes symlinks inside the pkgdir to things outside of it. It then runs a test with grep to fix the issue I raised. If the things outside the pkgdir don't exist, i.e. google-chrome isn't already installed as of the time that it's being built, the grep returns a non-zero exit and the sed thereafter doesn't execute.
You can fix this by running the grep with a "-q" which will return success on the first hit and will otherwise ignore errors. The sed is fine as is.
t3ddy commented on 2011-01-11 17:50 (UTC)
I don't want to say something stupid, but the pkgbuild corrects this. So, could it be a problem of cache? I don't know :/
dhaines commented on 2011-01-11 17:19 (UTC)
I installed this (via aurget) and /usr/share/applications/google-chrome.desktop points to /opt/google/chrome/google-chrome, while the actual executable (script) is at /opt/google-chrome/google-chrome. Thus, the Applications menu item no longer works.
t3ddy commented on 2011-01-08 11:48 (UTC)
Updated, sorry but I was away :)
Pinned Comments
gromit commented on 2023-11-30 17:09 (UTC)
When reporting this package as outdated make sure there is indeed a new version for Linux Desktop. You can have a look at the "Beta updates" tag in Release blog for this.
You can also run this command to obtain the version string for the latest chrome beta version:
Do not report updates for ChromeOS, Android or other platforms stable versions as updates here.