| Age | Commit message (Collapse) | Author |
|
|
|
vpm requires it to function
|
|
|
|
|
|
|
|
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.
|
|
|
|
It's a bit of a nitpick, but we might as well be consistent.
|
|
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.
|
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|