mirror of
https://github.com/ArchiveBox/ArchiveBox.git
synced 2026-04-25 17:16:00 +03:00
[GH-ISSUE #242] Chromium installed but not found by ./archive #167
Labels
No labels
expected: maybe someday
expected: next release
expected: release after next
expected: unlikely unless contributed
good first ticket
help wanted
pull-request
scope: all users
scope: windows users
size: easy
size: hard
size: medium
size: medium
status: backlog
status: blocked
status: done
status: idea-phase
status: needs followup
status: wip
status: wontfix
touches: API/CLI/Spec
touches: configuration
touches: data/schema/architecture
touches: dependencies/packaging
touches: docs
touches: js
touches: views/replayers/html/css
why: correctness
why: functionality
why: performance
why: security
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/ArchiveBox#167
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @fungalcofe on GitHub (May 18, 2019).
Original GitHub issue: https://github.com/ArchiveBox/ArchiveBox/issues/242
Describe the bug
./archivedon't findchromium-browsereven if it's installed.Steps to reproduce
pkg install chromium(successful installation)./archiveScreenshots or log output
[X] Missing dependency: chromium-browserHow I fixed it
I did a simple symbolic linck because it was looking for the wrong binary.
ln -s /usr/local/bin/chrome /usr/local/bin/chromium-browserSoftware versions
de28748Sidenote
It should be easily fixed. If I enjoy that tool and have some free time, I'll try to PR the installer to support FreeBSD.
@pirate commented on GitHub (May 20, 2019):
It tries all of these in order, so if it's not able to find it then it's probably not in your
$PATHor there's some other issue:What's the output of running
which chromium && chromium --versionin the same shell that you run ArchiveBox in?@fungalcofe commented on GitHub (May 20, 2019):
Hi,
For chrome:
For chromium-browser:
It works because I did a logical link to fix it:
To add
chromeor/usr/local/bin/chrometodefault_executable_pathscould the way to fix.@pirate commented on GitHub (May 20, 2019):
Just fixed this on
master:github.com/pirate/ArchiveBox@e2b714ba95Pull the latest version and comment back if you have any problems and I'll reopen the ticket.