Package Details: zed-editor-git 0.136.2.r48.g70888cf-1

Git Clone URL: https://aur.archlinux.org/zed-editor-git.git (read-only, click to copy)
Package Base: zed-editor-git
Description: A high-performance, multiplayer code editor from the creators of Atom and Tree-sitter
Upstream URL: https://zed.dev
Licenses: Apache-2.0, GPL-3.0-or-later, AGPL-3.0-or-later
Conflicts: zed-editor
Provides: zed-editor
Submitter: alerque
Maintainer: alerque
Last Packager: alerque
Votes: 3
Popularity: 1.50
First Submitted: 2024-03-20 17:58 (UTC)
Last Updated: 2024-05-17 09:01 (UTC)

Dependencies (23)

Required by (0)

Sources (1)

Latest Comments

alerque commented on 2024-05-17 08:57 (UTC)

Thanks @Zollerboy1. I didn't like the tested here-strings in that scripting but I see what it is doing, and that does get the job done. I adapted the scripting to be a bit more to my liking and adapted to the weird two-tier tag scheme Zed is using, but thanks for the pointer for getting that straightened out.

Zollerboy1 commented on 2024-05-14 20:02 (UTC)

Upstream is tagging releases out of line with the main branch, hence the weird versioning on this package. If anybody knows a sensible way to mainline the actual version relative to the branch point the tag used and still have a sensible counter I'd be up for it.

I had a similar problem with my package swift-format-git, as swift-format has their release tags in separate branches as well. I use this versioning counter, maybe you can adapt it here:

pkgver() {
    cd "$pkgname"
    local tags commit_count version
    tags="$(git tag --sort=-v:refname | grep -E '^[0-9]+\.[0-9]+\.[0-9]+$')"
    read -r commit_count version <<<"$(while IFS= read -r tag; do
        ancestor=$(git merge-base HEAD "$tag")
        commits_since=$(git rev-list "$ancestor..HEAD" --count)
        echo "$commits_since" "$tag"
    done <<< "$tags" | sort -nsu -k1,1 | head -1)"
    echo "$version.r$commit_count.$(git log --pretty=format:'%h' -n 1 HEAD)"
}

Fubwubs commented on 2024-05-07 20:56 (UTC) (edited on 2024-05-07 21:09 (UTC) by Fubwubs)

Got this error when building it:

error[E0554]: `#![feature]` may not be used on the stable release channel
 --> /home/me/.cargo/registry/src/index.crates.io-6f17d22bba15001f/proc-macro2-1.0.81/src/lib.rs:1:12
  |
1 | #![feature(proc_macro_byte_character)]
  |            ^^^^^^^^^^^^^^^^^^^^^^^^^

error[E0554]: `#![feature]` may not be used on the stable release channel
 --> /home/me/.cargo/registry/src/index.crates.io-6f17d22bba15001f/proc-macro2-1.0.81/src/lib.rs:2:12
  |
2 | #![feature(proc_macro_c_str_literals)]
  |            ^^^^^^^^^^^^^^^^^^^^^^^^^

I was able to build it successfully by switching to nightly (export RUSTUP_TOOLCHAIN=stable changed to export RUSTUP_TOOLCHAIN=nightly in the PKGBUILD). I think it might have been caused by this issue https://users.rust-lang.org/t/cannot-compile-simple-tokio-example/109956/5, which is just due to my system having a particular nightly compiler as default and won't affect anyone using stable as the default toolchain.

alerque commented on 2024-03-20 18:38 (UTC)

Upstream is tagging releases out of line with the main branch, hence the weird versioning on this package. If anybody knows a sensible way to mainline the actual version relative to the branch point the tag used and still have a sensible counter I'd be up for it.