Arch Linux User Repository

I have disabled the v up command, as it can break the installed package. v up changes the files in the resulting package after installation, meaning Pacman can't properly track its contents anymore.

I can't update the package to the latest version due to an error at the build-tools compilation stage.

---- Building cmd/tools ... ----------------------------------------------------------------------------------------------------------------
 OK    [ 1/70] C:   237.9 ms, R:     0.000 ms cmd/tools/changelog_helper.v
 OK    [ 2/70] C:   259.3 ms, R:     0.000 ms cmd/tools/bench/map_clear.v
......
 FAIL  [70/70] C:  2065.7 ms, R:     0.000 ms cmd/tools/vdoc
>> compilation failed:
/home/user/.vmodules/markdown/src/html_experimental.v:67:55: error: cannot use `u32` as `int` in argument 1 to `char.vstring_with_len`
   65 |         off := unsafe { attr.substr_offsets[i] }
   66 |         size := unsafe { attr.substr_offsets[i + 1] - off }
   67 |         text := unsafe { (attr.text + off).vstring_with_len(size) }
      |                                                             ~~~~
   68 | 
   69 |         match typ {

--------------------------------------------------------------------------------------------------------------------------------------------
To reproduce just failure 1 run:    '/home/user/code/aur/vlang/src/v-39534459885e916e2765b5b0c0ed66ce15f0ab86/v'  '/home/user/code/aur/vlang/src/v-39534459885e916e2765b5b0c0ed66ce15f0ab86/cmd/tools/vdoc'
Summary for building cmd/tools: 1 failed, 69 passed, 70 total. Elapsed time: 4254 ms, on 11 parallel jobs.
==> ERROR: A failure occurred in build().
    Aborting...

As far as I understand, when building vdoc, it optionally uses the markdown module, if it is installed. And the build breaks if the module itself is outdated. In theory, i can update local modules before updating vlang. But I don't think it's right that an uninstalled package gets into my user's home directory during the build. And that the build of the system package itself depends on files in the home directory. As an alternative, I suggest isolating the build in PKGBUILD, redefining the home directory. Then there will be no errors during the build. And the user will then be able to update the necessary local modules themselves.

build() {
    cd "v-${_v_commit_sha}"
    local tmpdir="/tmp/${pkgname}-${_v_commit_sha}"
    mkdir -p "$tmpdir" || { echo "Can't create temporary directory!"; exit 1; }

    # Delete directory when exiting function (even if there is an error)
    trap 'rm -rf "$tmpdir"' RETURN

    # Redefining HOME and TMPDIR for Isolation
    export HOME="$tmpdir"
    export TMPDIR="$tmpdir"
    CFLAGS="" LDFLAGS="" make prod=1 local=1

    # Compile all tools
    LDFLAGS='' ./v build-tools
}

Then the package is built successfully.

Please add libx11 as a make dependency, otherwise the v share tool fails to build in a clean chroot.

I have disabled the v up command, as it can break the installed package. v up changes the files in the resulting package after installation, meaning Pacman can't properly track its contents anymore.

Fails to build in clean chroot: https://termbin.com/44oj

The package has now been upgraded to 0.2.1. The only problem I've encountered so far is running v install <module>, but this is an upstream (resolved in master) bug and you can install modules using vlang-git if needed.

Edit: the problem persists on v 0.2.2, so this will need some investigation.

@div72 I just installed from git. After you install it from then on you just have to do v up

@div72 I expressed the current problems I'm having in this comment. I would appreciate help maintaining the package, and I just joined the Discord under my AUR username. Thank you.

@lberrymage What kind of problems are you having? I can help or maintain it if you want. Also could you join the discord?

@chovy

the vlang-git aur didn't compile for me.

If the vlang-git package is not compiling, please comment there rather than on this package.

I get this error after running v up it seemed to make the vlang binary disappear. How do I re-install it?

Re-install the whole package the way you originally did. Additionally, you shouldn't use v up since this pacman will maintain versions for you. Updating the binary forcefully will result in files not being tracked by pacman and thus the error you are seeing. To fix that specific error, run sudo rm /usr/lib/vlang/cmd/tools/vdoc and try installing again.

this is outdated.

Yes, I'm currently experiencing packaging problems with the new versions of v and haven't had sufficient time to work them out recently. If you have any suggestions feel free to share them, but please don't comment when the package is already marked out-of-date :).