| Git Clone URL: | https://aur.archlinux.org/vlang-git.git (read-only, click to copy) |
|---|---|
| Package Base: | vlang-git |
| Description: | Simple, fast, safe, compiled language for developing maintainable software (development version) |
| Upstream URL: | https://vlang.io |
| Keywords: | language programming v vlang |
| Licenses: | MIT |
| Conflicts: | v, vlang, vlang-bin |
| Provides: | vlang |
| Submitter: | whoami |
| Maintainer: | Chewing_Bever |
| Last Packager: | Chewing_Bever |
| Votes: | 1 |
| Popularity: | 0.038515 |
| First Submitted: | 2019-06-22 17:56 (UTC) |
| Last Updated: | 2024-04-10 14:01 (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.
If you wish to update your installation to the latest version, update this package instead.
@Zdrobot I doubt this has to do with this PKGBUILD. Yay and other AUR helpers don't update -git packages by default unless specified either as a CLI flag or in the config file.
TL;DR - this package installs the latest V from github, but does not update it after that.
I have installed this package, and V version was the same as on my other machine, where I've got V installed manually, as described in V documentation ( https://github.com/vlang/v/blob/master/doc/docs.md#linux-macos-freebsd-etc ): V 0.3.0 f0ce7fb
Then I updated V on the other machine with v up, and it pulled the latest commit from github and updated V to 0.3.0 f4b39fb. But on the machine where I have installed this package, yay did not update V, despite the fact there was a new commit out there.
@scottyeager Thanks for bringing this to my attention (and in great detail!); at first glance I think the cause is 17266ecb0786616e841cf25434d0bdfcaad91199 upstream. I'll start working on it.
Edit: The problem should be fixed in 0.2.2.r796.gfbc02cbc5-1.
I tried building today with version: vlang-git weekly.2021.8.r197.g204f57d22-1.
First, build() failed here:
./v -prod self
sh: line 1: vlang-git/src/vlang/cmd/tools/vself: No such file or directory
So I manually compiled vself.v:
cd src/vlang
./v -prod cmd/tools/vself.v
Then build() failed again at:
./v -prod self
Recompilation is disabled, since there is a "vlang-git/src/vlang/cmd/tools/.disable_autorecompilation" file present.
Please install V from source, to use `v self` .
I commented out the prepare() section of PKGBUILD where the .disable_autorecompilation file is created, and then building completed successfully.
/usr/lib/vlang/cmd/tools/ is no longer chmod 777-ed in 0.2.r418.g33976246c-4! A couple notes for those of you upgrading:
/usr/lib/vlang/cmd/tools/ before you can install the new version/usr/lib/vlang/cmd/tools/ to truly be fixed.@chovy This package actually isn't outdated since VCS packages update to the latest commit when the user installs them. They won't necessarily show the latest commit on the AUR, however. According to the Arch Wiki:
VCS packages are not considered out-of-date when the pkgver changes and are not to be flagged in this case.
https://wiki.archlinux.org/index.php/Arch_User_Repository#Flagging_packages_out-of-date
this is outdated. use vlang-bin
Produces
For usage information, quit V REPL and run v help
sh: /usr/lib/vlang/cmd/tools/vrepl: No such file or directoryI'm not sure what the devs were smoking... Not spending any more time on it, feel free to adopt.
@ragouel I have a solution for the permissions issue over on the vlang package - please feel free to adopt/adapt it so we don't need to chmod 777 :)
Pinned Comments
Chewing_Bever commented on 2022-08-07 07:30 (UTC)
I have disabled the
v upcommand, as it can break the installed package.v upchanges the files in the resulting package after installation, meaning Pacman can't properly track its contents anymore.If you wish to update your installation to the latest version, update this package instead.