On Wed, Feb 17, 2016 at 06:59:08PM +0000, Christopher Baines wrote:
> From a4d10c0c98b4b9b3df05951b9a38d37b8b1da6d3 Mon Sep 17 00:00:00 2001
> From: Christopher Baines <m...@cbaines.net>
> Date: Sat, 13 Feb 2016 23:49:25 +0000
> Subject: [PATCH] gnu: Add vcsh
>
> * gnu/packages/version-control.scm (vcsh): New variable.
[...]
> + (propagated-inputs
> + `(("git" ,git)))
I missed this earlier. We don't usually propagate this sort of "end-user
program" dependencies. For example rsync does not propagate ssh; the
user must install ssh. [0]
One problem is that the user may want to update git but not vcsh, or
vice versa. Multiple profiles would be required for the user to use
their desired version of git and vcsh.
Since vcsh's test suite requires git, I think it should be a native
input.
Your thoughts?
[0]
I know that ssh is not strictly required to use rsync, whereas it seems
that vcsh cannot work without git, but bear with me.
> + (home-page "https://github.com/RichiH/vcsh";)
> + (synopsis "Version control system for $HOME")
> + (description
> + "vcsh allows you to maintain several Git repositories in one single
> +directory. This can be useful when using version control for files in your
> +home directory, as it allows for the separation of the files into different
> +repositories, for example you may keep your bash configuration in a separate
> +Git repository from your emacs configuration.")
> + (license gpl2+)))
> --
> 2.7.0
>
