summarylogtreecommitdiffstats
path: root/PKGBUILD
AgeCommit message (Collapse)Author
2024-09-29bump version to 0.4.8Chewing_Bever
2024-07-28bump version to 0.4.7Chewing_Bever
2024-05-21Bump version to 0.4.6Chewing_Bever
2024-03-21Bump version to 0.4.5Chewing_Bever
2024-01-12Bump version to 0.4.4Chewing_Bever
2023-11-14Bump version to 0.4.3Chewing_Bever
2023-09-30Bump version to 0.4.2Jef Roosens
2023-09-04Bump version to 0.4.1Jef Roosens
2023-07-07Bump version to 0.4Chewing_Bever
2023-06-01Bump version to 0.3.4Chewing_Bever
2023-01-30Bump version to 0.3.3Chewing_Bever
2022-11-01Bumped version to 0.3.2Chewing_Bever
2022-08-31Updated to 0.3.1Jef Roosens
2022-08-07Disabled `v up`Chewing_Bever
2022-08-06Updated to version 0.3.0Chewing_Bever
2021-09-17Update from 0.2.2 to 0.2.4lberrymage
2021-01-22Utilize cmd/tools/.disable_autorecompilationlberrymage
This prevents the need to manually patch recompilation logic and additionally gives users a descriptive error message when trying to run `v up` or `v self`.
2021-01-22Update from 0.2.1 to 0.2.2lberrymage
2021-01-19Add openssl to optdependslberrymage
vpm requires it to function
2021-01-19Remove unnecessary dependency 'libcurl.so'lberrymage
2021-01-19Update from 0.1.29 to 0.2.1lberrymage
2020-08-06Update to version 0.1.29lberrymage
2020-07-22Use shorter patch to address no-compile.patchlberrymage
When building the package as one typically would via `makepkg`, no errors are encountered. However, when building in a clean chroot with the help of the `devtools` package, "no-compile.patch" cannot be found. Addressing the file as one directory "closer" to the current working directory solves this problem, and `makepkg` still finds the file due to a symlink it creates automatically. This will be useful for both testing the package and moving it to the community repository, should that ever happen.
2020-07-21Add vlang-bin as a conflicting packagelberrymage
2020-07-21Match package description with upstreamlberrymage
It's a bit of a nitpick, but we might as well be consistent.
2020-07-21Fix compilation error related to markdown modulelberrymage
Users were previously getting errors like the following when attempting to build the package: > 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) Although not obvious at first glance, this occured while building `vdoc`, as it requires the markdown module to be installed in the building user's home directory. This commit satisfies said requirement.
2020-07-21Add git to makedependslberrymage
2020-07-19Use sha256sums instead of md5sumslberrymage
2020-07-19Update to version 0.1.28.1lberrymage
It is required to manually checkout a specific revision of `vc` as the latest release tarball for `vc` is 0.1.20. The revision checked out corresponds exactly to the current release of `v`. There are GitHub issues upstream addressing this issue and a solution is in the works.
2020-01-09Updated sha256sumsFelix Golatofski
2019-09-17Update to v0.1.20László Várady
2019-09-17Update to v0.1.19László Várady
2019-07-31up 0.1.17whoami
2019-07-18fix for future V release: examples/hot_code_reloading/bounce.vwhoami
2019-07-17updatewhoami
2019-07-17up 0.1.15whoami
2019-06-22initial commit. Not ready for use. Waiting for public releasewhoami