Package Details: vlang 0.2.2-2

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, vlang-bin, vlang-git
Submitter: whoami
Maintainer: lberrymage
Last Packager: lberrymage
Votes: 11
Popularity: 0.040116
First Submitted: 2019-06-22 16:53
Last Updated: 2021-01-23 08:16

Pinned Comments

lberrymage commented on 2021-01-20 05:06

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.

Latest Comments

1 2 3 Next › Last »

lberrymage commented on 2021-01-20 05:06

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.

chovy commented on 2021-01-12 05:44

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

lberrymage commented on 2021-01-12 05:41

@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.

div72 commented on 2021-01-10 19:00

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

lberrymage commented on 2021-01-02 11:18

@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 :).

chovy commented on 2021-01-02 01:17

this is outdated.

chovy commented on 2020-12-31 11:51

I get this error after running v up it seemed to make vlang binary disappear.

How do I re-install it?

Total Installed Size:  15.34 MiB

:: Proceed with installation? [Y/n] 
(1/1) checking keys in keyring                                                                                   [###################################################################] 100%
(1/1) checking package integrity                                                                                 [###################################################################] 100%
(1/1) loading package files                                                                                      [###################################################################] 100%
(1/1) checking for file conflicts                                                                                [###################################################################] 100%
error: failed to commit transaction (conflicting files)
vlang: /usr/lib/vlang/cmd/tools/vdoc exists in filesystem
Errors occurred, no packages were upgraded.

chovy commented on 2020-12-31 10:52

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

1ace commented on 2020-12-29 14:38

@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

@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.