Package Details: vcsh-git 1:1.20151229.1.r0.g87bccfd-1

Git Clone URL: (read-only)
Package Base: vcsh-git
Description: manage config files in HOME via fake bare git repositories
Upstream URL:
Licenses: GPL
Conflicts: vcsh
Provides: vcsh
Submitter: Dieter_be
Maintainer: xaocon
Last Packager: xaocon
Votes: 10
Popularity: 0.000000
First Submitted: 2011-11-20 12:14
Last Updated: 2016-01-24 18:34

Dependencies (3)

Required by (2)

Sources (1)

Latest Comments

vlowrian commented on 2015-05-26 20:29

Some unit tests added new dependencies. If you compile this on a fresh system, you also need perl-shell-command (AUR) and perl-test-most (AUR). Please add those dependencies.

xaocon commented on 2014-06-23 07:21

I've taken over the package. I've added ronn back because the static branch doesn't seem to always match master and I preferred building for yourself for the -git package. I'll track how future commits are handled.

chetgray commented on 2014-06-12 21:31

Upstream is building manpages in the manpage-static branch. Pulling source from that branch, ruby-ronn is no longer a build requirement. I don't use vcsh any more, so I'm disowning. Feel free to take over.

pspeder commented on 2014-05-26 08:56

I resolved it by un- and then reinstalling ruby-ronn from aur.

chetgray commented on 2014-02-09 16:26

Someone is having the same issue with the non-devel vcsh package. I wasn't able to replicate, but I'll try some more.

vcsh.1 is generated in the Makefile from vcsh.1.ronn with ronn from ruby-ronn. If vcsh.1 isn't found by install, then its generation may have been prevented by a problem with ronn or the Makefile.

kodiak commented on 2014-02-09 15:14

with newest version I get: "install: cannot stat ‘vcsh.1’: No such file or directory"

xaocon commented on 2013-09-24 14:24

Yeah I saw it was building from HEAD. I just know that people use automated tools that don't rebuild until there is a version bump. Of course, how you want to handle versions is up to you. Glad I could help.

chetgray commented on 2013-09-24 08:42

Tagged release PKGBUILD now in AUR:

chetgray commented on 2013-09-24 02:30

Thanks for the heads-up on mr->myrepos and GPL2+. I'll update the PKGBUILD later today. As for there being more recent tagged released, that is irrelevant as this PKGBUILD pulls the HEAD commit from git.

xaocon commented on 2013-09-23 17:17

the optdepends for this has changed names to myrepos both on the site and in the AUR. This should also probably get a version bump as there have been tagged releases since this one.

Anonymous comment on 2013-09-02 20:52

BTW, the license is GPL2+, not GPL2.

Anonymous comment on 2013-08-28 20:08

Hi chetgray,

that layout makes a lot of sense. I obviously release when I feel that there's a need, but HEAD in master is always usable, so...

Thanks for the update,

chetgray commented on 2013-08-25 23:03

Thanks, RichiH. The PKGBUILD automatically pulls in the HEAD from your github repo, so people building pkgs from it will always have the latest updates. AUR's web interface parses out the version from the PKGBUILD itself, so 2013.04.23_11.42_0871cff-1 is just when I last updated the PKGBUILD, not what version of vcsh is packaged.

It is trivial to peg the PKGBUILD to a particular commit. In fact, I have a branch of the PKGBUILD that pulls only the latest tagged release commit from your git repo, not the HEAD commit. At some point I'll upload it to AUR as a 'vcsh' PKGBUILD, keeping this one as vcsh-git for those folks who want a devel version of vcsh.

Anonymous comment on 2013-07-24 22:18

Upstream here.

I didn't know my versioning scheme caused issues on your side, sorry for that. FWIW, I decided to switch back to a date-based one. There've been a few upstream releases since the last package update to AUR and I would obviously like to see the most current one make its way into AUR.

If you need a version with a pre-compiled manpage, look at the homebrew branch. If you need your own release branch and/or prefer a more neutral name than homebrew for that branch, please let me know.

I will try to monitor this page, but poking me on IRC or GitHub is more reliable.


chetgray commented on 2013-04-28 23:17

Cheers, joni. I've already made some of that changover, but haven't upped the result. I'll incorporate yours and upload shortly.

joni commented on 2013-04-28 21:56

I edited the PKGBUILD to use the new vcsh handling in makepkg:
No pkgver hacks needed anymore.

chetgray commented on 2013-03-14 02:02

Hackish reassignment of pkgver at the end of the PKGBUILD, but it worked to fool AUR.

I tried to keep the previous versioning scheme (YYYY.MM.DD), with automatic updating to the date of the latest commit (not today's date, as makepkg is wont to do, and with the addition of time and unique SHA1. This should keep versioning ordered correctly.

chetgray commented on 2013-03-13 04:53

I have a working PKGBUILD, which updates pkgver better than makepkg currently does. AUR's pkgsubmit script, however, misparses the pkgver variable (re)assignment in build() and thinks the package has an extremely long pkgver string, refusing the upload. I'll work it out tomorrow, and likely submit a bug on AUR.

chetgray commented on 2013-03-13 04:52

I have a working PKGBUILD, which updates pkgver better than makepkg currently does. AUR's pkgsubmit script, however, misparses the pkgver variable (re)assignment in build() and thinks the package has an extremely long pkgver string, refusing the upload. I'll work it out tomorrow.

Dieter_be commented on 2013-03-05 15:11

disowned. feel free to adopt, Nico (or anyone else)

npouillard commented on 2013-03-05 13:39

pkgtools seems to no longer provide ronn.

Dieter_be commented on 2012-04-09 11:46

if I run `makepkg -si` on a new arch installation, it works fine?

Anonymous comment on 2012-04-04 11:13

ronn depends in turn on

ruby-hpricot ruby-rdiscount ruby-mustache

which I also didn't have.

jryan commented on 2012-02-11 07:04

Depends on ronn, build for me failed because ronn was not a depends.