Please add git
and libx11
as a make dependency, otherwise it fails to build in a clean chroot.
Search Criteria
Package Details: vlang-bin 0.4.9-2
Package Actions
Git Clone URL: | https://aur.archlinux.org/vlang-bin.git (read-only, click to copy) |
---|---|
Package Base: | vlang-bin |
Description: | Simple, fast, safe, compiled language for developing maintainable software (binary release) |
Upstream URL: | https://vlang.io |
Keywords: | language programming v vlang |
Licenses: | MIT |
Conflicts: | v, vlang, vlang-git |
Provides: | vlang |
Submitter: | ragouel |
Maintainer: | Chewing_Bever |
Last Packager: | Chewing_Bever |
Votes: | 5 |
Popularity: | 0.113336 |
First Submitted: | 2020-03-17 22:41 (UTC) |
Last Updated: | 2025-01-02 08:39 (UTC) |
Dependencies (5)
- glibc (glibc-gitAUR, glibc-linux4AUR, glibc-eacAUR, glibc-eac-binAUR)
- libx11 (libx11-gitAUR) (make)
- freetype2 (freetype2-macosAUR, freetype2-gitAUR, freetype2-qdoledAUR) (optional) – Needed for graphics support
- glfw (glfw-wayland-minecraft-cursorfixAUR, glfw-gitAUR, glfw-waywallAUR) (optional) – Needed for graphics support
- openssl (openssl-gitAUR, openssl-staticAUR) (optional) – Needed for http support
Required by (8)
- compass-status-git (requires vlang) (make)
- crepl-git (requires vlang) (make)
- v-analyzer-bin (requires vlang)
- v-analyzer-git (requires vlang)
- vieter (requires vlang) (make)
- vieter-git (requires vlang) (make)
- vlang-coreutils-git (requires vlang) (make)
- vlogsolv (requires vlang) (make)
Sources (1)
SunRed commented on 2024-12-27 12:47 (UTC)
lberrymage commented on 2021-01-20 05:09 (UTC) (edited on 2021-01-20 05:09 (UTC) by lberrymage)
The only way I was able to make it run, was to grant 777 recursively on /usr/lib/vlang/cmd, which is a potential security risk. Use at your own risk.
We should be able to solve the chmod 777
problem once upstream cuts a new release. See this commit.
1ace commented on 2021-01-02 13:20 (UTC) (edited on 2021-01-02 13:25 (UTC) by 1ace)
@chovy: you seem to be misunderstanding the point of v up
and what a package manager is and does. I encourage you to read up on those, and you'll understand why you must never run v up
(unless you want to break your system) :)
Edit (to be clearer): v up
does have a reason to exist, as it is useful in two cases: when you don't have a package manager (eg. on Windows), or if you don't want to (or can't) install v
system-wide (eg. you are on the someone else's machine and you don't have permission to install packages, so you just install v
in your user's home folder).
chovy commented on 2021-01-02 13:02 (UTC)
sudo v up
still updated it. I guess that is newer than what yay -S vlang-bin
installs.
lberrymage commented on 2021-01-02 11:00 (UTC)
@chovy It requires sudo
because this package installs v
in a system directory which requires superuser permissions to write to. This shouldn't be a problem if you're using this package though since you should upgrade via pacman
, not v up
.
chovy commented on 2021-01-02 01:15 (UTC)
How come v up
requires sudo v up
to work? The vlang guys say this shouldn't be required.
1ace commented on 2020-12-26 10:14 (UTC)
Adding to my out-of-date message, sed s/0.1.29/0.2/ -i PKGBUILD && updpkgsums && mksrcinfo
is enough to update the package :)
ragouel commented on 2020-07-20 16:25 (UTC)
@lberrymage Touch away...
lberrymage commented on 2020-07-20 16:02 (UTC)
Oh wait... this is the -bin
package. The other workaround is to touch
each binary in the cmd/tools directory so their mtime is later than that of their respective source code.
Pinned Comments
lberrymage commented on 2021-01-20 05:09 (UTC) (edited on 2021-01-20 05:09 (UTC) by lberrymage)
We should be able to solve the
chmod 777
problem once upstream cuts a new release. See this commit.ragouel commented on 2020-06-13 02:07 (UTC)
The only way I was able to make it run, was to grant 777 recursively on
/usr/lib/vlang/cmd
, which is a potential security risk. Use at your own risk.