Package Details: vlang 0.2.4-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, vlang-bin, vlang-git
Submitter: whoami
Maintainer: lberrymage
Last Packager: lberrymage
Votes: 12
Popularity: 0.026823
First Submitted: 2019-06-22 16:53 (UTC)
Last Updated: 2021-09-17 08:51 (UTC)

Pinned Comments

lberrymage commented on 2021-01-20 05:06 (UTC) (edited on 2021-01-23 07:40 (UTC) by lberrymage)

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

mags commented on 2022-03-25 19:11 (UTC)

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

lberrymage commented on 2021-01-20 05:06 (UTC) (edited on 2021-01-23 07:40 (UTC) by lberrymage)

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 (UTC)

@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 (UTC)

@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 (UTC)

@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 (UTC)

@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 (UTC)

this is outdated.

chovy commented on 2020-12-31 11:51 (UTC)

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

kseistrup commented on 2020-07-21 20:07 (UTC)

@lberrymage

I don't know anything about vlang, I only have it installed because it is (or was?) a build dependency of another package.

Running “v install markdown” didn't work because apparently v needs vpm, that wasn't built yet. But after the previously mentioned error I could run “src/v-0.1.28.1/v_old install markdown” successfully and the go back to “makepkg -s” to build the package.

Thanks.

lberrymage commented on 2020-07-21 19:08 (UTC)

@tyrannis.hawk I've added git to makedepends now. For some reason I keep thinking it's in base-devel...

@kseistrup The markdown module in required when building vdoc. Since modules are installed in the user's home directory by default, I already had it installed from previous testing unknowingly. I will try to fix this hopefully later today. If you want to work around it in the meantime, build v straight from the git repository and run v install markdown. You should be able to install the vlang package afterwards.

kseistrup commented on 2020-07-21 11:03 (UTC)

vlang 0.1.28.1-2 does not build here:

V self compiling (-prod)...
builder error: cannot import module "markdown" (not found)
==> ERROR: A failure occurred in build().
    Aborting...
error making: %!s(func() string=0x55b93b10ba60)

tyrannis.hawk commented on 2020-07-21 09:37 (UTC)

If you are using

git checkout 197b42bd0e9268ec7c3c16526edc8530ad90a075

or other git commands in your PKGBUILD, you need to add git as a makedepends, otherwise your package will fail to build in a clean build environment.

Could you please add it?

lberrymage commented on 2020-07-04 05:05 (UTC)

I noticed today that the package is flagged out-of-date (don't know why I didn't get an AUR email), and I appreciate the notice. However, I'm running into issues packaging v now because it does not compile cmd tools on installation, instead building them lazily. This doesn't work without 777 access to /usr/lib/vlang/cmd/tools and we obviously can't allow that. I'm attempting to work around this, but between other various packaging issues due to v itself, its current development status, and its design for installation as a whole, v is quite difficult to install in a system directory.

I still plan to update the package in the next few days; hold tight.

whoami commented on 2019-07-16 22:19 (UTC)

version up 0.1.15

whoami commented on 2019-06-26 22:27 (UTC)

vlang not linux-friendly yet. It's deep alpha. Compile vlang from git manually for awhile

whoami commented on 2019-06-24 09:49 (UTC)

not released yet, so use vlang-git before release