From: ludo@gnu.org (Ludovic Courtès)
To: "Stefan Reichör" <stefan@xsteve.at>
Cc: 28531-done@debbugs.gnu.org
Subject: bug#28531: [PATCH] gnu: Add vcsh.
Date: Wed, 20 Sep 2017 22:32:09 +0200 [thread overview]
Message-ID: <87a81pru0m.fsf@gnu.org> (raw)
In-Reply-To: <150593626773.31985.7642001649222018304.stgit@sandburg> ("Stefan \=\?utf-8\?Q\?Reich\=C3\=B6r\=22's\?\= message of "Wed, 20 Sep 2017 21:37:47 +0200")
[-- Attachment #1: Type: text/plain, Size: 426 bytes --]
Hi Stefan,
Stefan Reichör <stefan@xsteve.at> skribis:
> * gnu/packages/version-control.scm (vcsh): New variable.
Pushed with the minor changes below (the first sentence of the
description looked awkward to me).
Note that vcsh takes ‘git’ from $PATH. I wonder if we should keep it
this way, or if we should hard-code the absolute file name to ‘git’ so
that it always works.
Thoughts?
Ludo’.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Type: text/x-patch, Size: 1633 bytes --]
diff --git a/gnu/packages/version-control.scm b/gnu/packages/version-control.scm
index 424907332..78e142b29 100644
--- a/gnu/packages/version-control.scm
+++ b/gnu/packages/version-control.scm
@@ -726,9 +726,10 @@ manipulate them in various ways.")
(base32
"1ym3swkh738c3vciffvlr96vqzhwmzkb8ajqzap8f0j9n039a1mf"))))
(build-system gnu-build-system)
+ (native-inputs
+ `(("which" ,which)))
(inputs
`(("git" ,git)
- ("which" ,which)
("perl" ,perl)
("perl-test-harness" ,perl-test-harness)
("perl-shell-command" ,perl-shell-command)
@@ -741,12 +742,13 @@ manipulate them in various ways.")
(assoc-ref %outputs "out")))
#:test-target "test"))
(home-page "https://github.com/RichiH/vcsh")
- (synopsis "Version Control System for $HOME")
+ (synopsis "Version control system for @code{$HOME}")
(description
- "Maintain several Git repositories in one single directory. They all
-maintain their working trees without clobbering each other or interfering
-otherwise. By default, all Git repositories maintained via vcsh store the
-actual files in $HOME. But this can be overridden.")
+ "vcsh version-controls configuration files in several Git repositories,
+all in one single directory. They all maintain their working trees without
+clobbering each other or interfering otherwise. By default, all Git
+repositories maintained via vcsh store the actual files in @code{$HOME},
+though this can be overridden.")
(license license:gpl2+)))
(define-public git-test-sequence
next prev parent reply other threads:[~2017-09-20 20:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-20 19:37 [bug#28531] [PATCH] gnu: Add vcsh Stefan Reichör
2017-09-20 20:32 ` Ludovic Courtès [this message]
[not found] ` <87o9q2o1bw.fsf@xsteve.at>
2017-09-23 12:52 ` Ludovic Courtès
2017-09-23 18:10 ` Stefan Reichör
2017-09-25 9:50 ` Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a81pru0m.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=28531-done@debbugs.gnu.org \
--cc=stefan@xsteve.at \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).