Aditya Kumar
45d4de75b3
## Error ```sh ./script/install-linux + [[ 0 -gt 0 ]] + export ZED_CHANNEL=dev + ZED_CHANNEL=dev ++ pwd + export 'ZED_UPDATE_EXPLANATION=You need to fetch and rebuild zed in /home/adityakrcodes/repos/zed' + ZED_UPDATE_EXPLANATION='You need to fetch and rebuild zed in /home/adityakrcodes/repos/zed' + script/bundle-linux + getopts h flag + export ZED_BUNDLE=true + ZED_BUNDLE=true + channel=dev ++ script/get-crate-version zed script/get-crate-version: line 16: jq: command not found <-- ERROR + version= ``` The script fails to install zed on Arch Linux due to a missing dependency, `jq`. ## My machine info OS: Arch Linux Kernel: 6.6.34-1-lts WM: dwm Terminal: kitty CPU: Ryzen 5 5500U with Radeon Graphics GPU: AMD ATI 04:00.0 Lucienne Memory: 16 GB ## Error Description The error occurs when running the script in `script/install-linux`, which is unable to find the `jq` package, which is not installed by default on the machine. ## Solution To resolve this issue, you can install `jq` independently by running `sudo pacman -S jq`. Alternatively, I have updated script `script/linux` to include `jq` as a dependency ([link to the commit](https://github.com/adityakrcodes/zed/commit/2349ad111f48bf8c571e3710bdb317ee151fabdb)), ensuring it is installed automatically when running the initial script for system libraries. Release Notes: - N/A
Zed
Welcome to Zed, a high-performance, multiplayer code editor from the creators of Atom and Tree-sitter.
Installation
You can download Zed today for macOS (v10.15+).
Support for additional platforms is on our roadmap:
- Linux (tracking issue)
- Windows (tracking issue)
- Web (tracking issue)
For macOS users, you can also install Zed using Homebrew:
brew install --cask zed
Alternatively, to install the Preview release:
brew install --cask zed@preview
Developing Zed
- Building Zed for macOS
- Building Zed for Linux
- Building Zed for Windows
- Running Collaboration Locally
Contributing
See CONTRIBUTING.md for ways you can contribute to Zed.
Also... we're hiring! Check out our jobs page for open roles.
Licensing
License information for third party dependencies must be correctly provided for CI to pass.
We use cargo-about to automatically comply with open source licenses. If CI is failing, check the following:
- Is it showing a
no license specifiederror for a crate you've created? If so, addpublish = falseunder[package]in your crate's Cargo.toml. - Is the error
failed to satisfy license requirementsfor a dependency? If so, first determine what license the project has and whether this system is sufficient to comply with this license's requirements. If you're unsure, ask a lawyer. Once you've verified that this system is acceptable add the license's SPDX identifier to theacceptedarray inscript/licenses/zed-licenses.toml. - Is
cargo-aboutunable to find the license for a dependency? If so, add a clarification field at the end ofscript/licenses/zed-licenses.toml, as specified in the cargo-about book.