Package Details: vcsh 1.20151229-3

Git Clone URL: https://aur.archlinux.org/vcsh.git (read-only, click to copy)
Package Base: vcsh
Description: manage config files in HOME via fake bare git repositories
Upstream URL: https://github.com/RichiH/vcsh
Licenses: GPL
Submitter: chetgray
Maintainer: caleb
Last Packager: caleb
Votes: 24
Popularity: 0.32
First Submitted: 2013-09-24 08:41
Last Updated: 2020-02-24 06:58

Dependencies (2)

Required by (2)

Sources (1)

Pinned Comments

caleb commented on 2020-02-24 06:51

PSA: I've started hosting this as a prebuilt package in my repository for those that want to install it using pacman without messing around with building from the AUR.

Latest Comments

« First ‹ Previous 1 2

caleb commented on 2014-02-11 12:04

Yes, it is a problem with running RONN. I have successfully petitioned to get that step moved upstream so it is not a build time dependency. The next release shouldn't need that step. See https://github.com/RichiH/vcsh/issues/104

chetgray commented on 2014-02-06 23:09

caleb, I cannot replicate. The only modifications to the PKGBUILD since the last version were to bump the pkgver and explicitly set ZSHDIR so completion functions are installed correctly for Arch.

Perhaps vcsh.1 is not being generated for you? Are you receiving the error when running makepkg from a clean directory with only the PKGBUILD in it?

chetgray commented on 2014-02-06 21:21

Hmm, it was working for me. I'll check it out later today.

caleb commented on 2014-02-05 11:20

2014-02-05 version does not build for me, you seem to have broken something to do with the man page. I know the use of ronn in the makefile is a pain, but it worked in the last version of this package and is broken now:

install: cannot stat ‘vcsh.1’: No such file or directory
Makefile:14: recipe for target 'install' failed
make: *** [install] Error 1

caleb commented on 2014-02-05 11:14

Thanks for the version bump.

I am aware of the dev package and how it works. Having to rebuild the package from git every time you check a system for upgrades is unsuitable for production environments, which is part of why this package that actually has a meaningful version number kept up to date is necessary.

chetgray commented on 2014-02-05 05:50

Whoops, I had a typo in the Github feed URL.

For what it's worth, the vcsh-git PKGBUILD is not out of date, and automatically pulls the latest commit when (re)packaged.

caleb commented on 2014-02-03 12:42

I would be interested in maintaining this package to keep up with the latest releases (I am also involved in vcsh development). If you do not plan on tracking the latest builds would you be willing to disown it so that I can?