Search Criteria
Package Details: typst-lsp 0.10.1-1
Package Actions
- View PKGBUILD / View Changes
- Download snapshot
- Search wiki
- Flag package out-of-date
- 1 pending request
- Submit Request
Git Clone URL: | https://aur.archlinux.org/typst-lsp.git (read-only, click to copy) |
---|---|
Package Base: | typst-lsp |
Description: | Language server for Typst |
Upstream URL: | https://github.com/nvarner/typst-lsp |
Licenses: | MIT, Apache |
Submitter: | Chocobo1 |
Maintainer: | Chocobo1 |
Last Packager: | Chocobo1 |
Votes: | 2 |
Popularity: | 0.35 |
First Submitted: | 2023-04-05 18:23 (UTC) |
Last Updated: | 2023-09-22 18:23 (UTC) |
Dependencies (2)
- gcc-libs (gccrs-libs-git, gcc-libs-git, gcc11-libs)
- rust (rust-nightly, rust-nightly-bin, rust-git, rustup-git, rustup) (make)
Latest Comments
alerque commented on 2023-06-21 23:38 (UTC) (edited on 2023-06-21 23:38 (UTC) by alerque)
If you can't be bothered to follow packaging guidelines can you please consider disowning or at least adding me as a co-maintainer yet. This package doesn't have enough usage yet for me to justify moving it to official repos. If we get some votes and/or usage showing up in pkgstats I will probably do that eventually.
Also it can't be that much of a bother to copy the patch I sent to a file and apply it with a single command, then push it. I already handled all the guideline fixes for you.
Chocobo1 commented on 2023-06-19 17:00 (UTC)
Lets say I have other considerations and I don't really want to deal with it. Could you please consider bringing this package into (arch) official repo and maintain it? I believe it would be the best for all users.
alerque commented on 2023-06-15 20:01 (UTC)
This patch can be saved to a file and applied with
git am file.patch
and covers the issues I mentioned:alerque commented on 2023-06-15 06:32 (UTC)
Can you please overhaul this a bit to follow the Arch Rust package guidelines. Just on a quick inspection there are quite a few things missing. First, upstream has a lock file so use it, don't silently create it if missing. If they miss it or don't update it it should fail. Also the fetch should be limited to the architecture. Then a build function should be added and used instead of
cargo install
(unless that is absolutely unavoidable). A couple of environment variables also need setting to get the right toolchain in case people have defaulted to a nightly Rust toolchain, etc. The Wiki explains all these.