Package Details: vlang 0.4.5-1

Git Clone URL: https://aur.archlinux.org/vlang.git (read-only, click to copy)
Package Base: vlang
Description: Simple, fast, safe, compiled language for developing maintainable software
Upstream URL: https://vlang.io
Keywords: language programming v vlang
Licenses: MIT
Conflicts: v
Submitter: whoami
Maintainer: Chewing_Bever
Last Packager: Chewing_Bever
Votes: 16
Popularity: 0.074535
First Submitted: 2019-06-22 16:53 (UTC)
Last Updated: 2024-03-21 09:57 (UTC)

Dependencies (5)

Sources (2)

Pinned Comments

Chewing_Bever commented on 2022-08-07 07:25 (UTC)

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.

Latest Comments

« First ‹ Previous 1 2 3 Next › Last »

chovy commented on 2020-12-31 10:52 (UTC)

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

1ace commented on 2020-12-29 14:38 (UTC)

@lberrymage: yeah, I realized my patch didn't actually work, so I deleted my comment. I should've tested it better before posting anything.

I'm not a vlanger yet, I've been meaning to get into this language as it looks promising, but I don't think I know enough to actually help with this issue, sorry :(
If I happen to have an idea though, I'll test it and share here :)

lberrymage commented on 2020-12-29 06:16 (UTC)

@1ace The problem I'm currently experiencing is related to installing the markdown module, which is required to build vdoc.

If you already have it installed (in ~/.vmodules/markdown, it's super easy to update to 0.2. If you don't have it installed, the markdown module doesn't install with either cgen error while compiling vpm (nothing else, even in verbose mode) or http.fetch: invalid url while installing the markdown module with vpm. The end result is that if you already have vlang installed (and most likely the markdown module), only a .SRCINFO/pkgsums/pkgver etc. change is required. Otherwise, vdoc can't compile.

I've been busy over Christmas and all, so I should be able to give more attention to this in coming days.

If you happen to come up with a patch and/or suggestions I'll be glad to accept either. Thank you for offering.

1ace commented on 2020-12-26 09:59 (UTC)

0.2 is now out (and I can't re-flag as out of date ^^')

I'm also happy to help with packaging if you want :)

lberrymage commented on 2020-12-12 01:09 (UTC) (edited on 2020-12-15 08:37 (UTC) by lberrymage)

I'll get around to updating to 0.1.30 this Sunday or Monday - thank you for the notice @sunng.

Update: Packaging issues concerning v's compilation process kindly request your further patience :).

kseistrup commented on 2020-07-22 06:51 (UTC)

Amazing, thanks!

lberrymage commented on 2020-07-22 04:29 (UTC)

@kseistrup The issue should be fixed for everyone now.

lberrymage commented on 2020-07-21 20:12 (UTC)

@kseistrup Ah, sorry, I meant ./v install markdown (so you're running the copy of v made from the git repo).

Good to hear you figured it out.