Re: [RFR] templates://gitolite/{templates}
Jonathan Wiltshire wrote:
> There are no changes to debian/control, although I'm not sure about the
> section talking of "dedication"; I'm hoping somebody will give me some
> ideas about that.
> --- ../gitolite.old/debian/templates 2010-07-01 19:56:02.000000000 +0100
> +++ debian/templates 2010-07-01 20:17:23.000000000 +0100
> @@ -1,22 +1,24 @@
> Template: gitolite/gituser
> Type: string
> Default: gitolite
> -_Description: The name of the system user to create:
> +_Description: System user to use:
>
> It might already be created.
Overused "use". Replace it with some extra context:
_Description: System username for gitolite:
[...]
> Template: gitolite/adminkey
> Type: string
> +_Description: Administrator's SSH key:
> Please specify the key of the user that will administer the access
> + configuration of gitolite.
> + .
> + The installer can accept the SSH public key directly, or the path to a file
> + containing it. If blank, the installer will not configure gitolite and it
> + must be set up manually.
>
> Keep the second person out again.
Ditto "the installer" (and the dangling modifier "if blank"):
This can be either the SSH public key itself, or the path to a file
containing it. If it is blank, gitolite will be left unconfigured and
must be set up manually.
In the control file:
> Package: gitolite
> Architecture: all
> Depends: git (>= 1:1.7.0.4) | git-core (>= 1:1.6.2), perl (>= 5.6.0-16),
> openssh-server | ssh-server, debconf (>= 0.5) | debconf-2.0, adduser
> Suggests: git-daemon-run, gitweb
> Description: ssh-based gatekeeper for git repositories
SSH
> Gitolite is an ssh-based gatekeeper for a server that hosts many git
SSH
> repositories, and that needs access control of some sort.
How about turning that round as "Gitolite is an SSH-based gatekeeper
providing access control for a server that hosts many git
repositories"?
> Without gitolite,
> each developer needing to push to one of the repositories hosted will need a
would
> (Unix) userid and password on that server;
Just say:
user account on the server;
> gitolite let you do that just using
lets
> ssh public keys tied to a single, common, user that hosts all the
SSH
> repositories.
Or say:
gitolite replaces this with SSH
public keys tied to a single user that hosts all the repositories.
> .
> What makes gitolite unique is its dedication: Its primary target is corporate
> environments where the ability to restrict who can push to what branch is also
> important. It has grown beyond that initial motivation to write it and
> acquired several other neat features that you can find described in the main
> README.
"Dedication" is a slightly odd choice of word... but it's hard to
find a direct replacement. Perhaps instead of focussing on the
project's historical development we could import the list of neat
features from that README:
Gitolite can restrict who can read (clone/fetch) from or write
(push) to a repository, and who can push to what branch or tag - an
important issue in corporate environments. Other features include:
* access control by branch-name or by modified file/directory;
* per-developer "personal namespace" prefixes;
* simple but powerful configuration file syntax (with validation);
* config files (and authority for maintaining them) can be split;
* easy integration with gitweb;
* comprehensive logging;
* easy migration from gitosis.
--
JBR with qualifications in linguistics, experience as a Debian
sysadmin, and probably no clue about this particular package
--- ../gitolite-1.5.3.pristine/debian/templates 2010-07-02 07:26:46.000000000 +0100
+++ debian/templates 2010-07-02 07:29:50.000000000 +0100
@@ -1,22 +1,24 @@
Template: gitolite/gituser
Type: string
Default: gitolite
-_Description: The name of the system user to create:
+_Description: System user for gitolite:
Please enter the name for the system user which should be used by
- gitolite.
+ gitolite. It will be created if necessary, and its home
+ directory will be used to store repositories.
Template: gitolite/gitdir
Type: string
Default: /var/lib/gitolite
-_Description: The directory to contain the repositories:
- Please enter the path for the directory in which you want to store the
- git repositories guarded by gitolite. This will also become the home
- of the former entered username.
+_Description: Repository path:
+ Please enter the path in which the gitolite repositories should be stored.
+ This will be set as the system user's home directory.
Template: gitolite/adminkey
Type: string
-_Description: The key for the admin user:
+_Description: Administrator's SSH key:
Please specify the key of the user that will administer the access
- configuration of gitolite. You can either give the filename or paste
- the ssh public key. Leave empty if you do not want to set up gitolite
- in the directory specified earlier.
+ configuration of gitolite.
+ .
+ This can be either the SSH public key itself, or the path to a file
+ containing it. If it is blank, gitolite will be left unconfigured and
+ must be set up manually.
--- ../gitolite-1.5.3.pristine/debian/control 2010-07-02 07:26:46.000000000 +0100
+++ debian/control 2010-07-02 07:36:19.000000000 +0100
@@ -14,16 +14,20 @@
Depends: git (>= 1:1.7.0.4) | git-core (>= 1:1.6.2), perl (>= 5.6.0-16),
openssh-server | ssh-server, debconf (>= 0.5) | debconf-2.0, adduser
Suggests: git-daemon-run, gitweb
-Description: ssh-based gatekeeper for git repositories
- Gitolite is an ssh-based gatekeeper for a server that hosts many git
- repositories, and that needs access control of some sort. Without gitolite,
- each developer needing to push to one of the repositories hosted will need a
- (Unix) userid and password on that server; gitolite let you do that just using
- ssh public keys tied to a single, common, user that hosts all the
- repositories.
+Description: SSH-based gatekeeper for git repositories
+ Gitolite is an SSH-based gatekeeper providing access control for a server that
+ hosts many git repositories. Without gitolite, each developer needing to push
+ to one of the repositories hosted would need a user account on the server;
+ gitolite replaces this with SSH public keys tied to a single user that hosts
+ all the repositories.
.
- What makes gitolite unique is its dedication: Its primary target is corporate
- environments where the ability to restrict who can push to what branch is also
- important. It has grown beyond that initial motivation to write it and
- acquired several other neat features that you can find described in the main
- README.
+ Gitolite can restrict who can read (clone/fetch) from or write (push) to a
+ repository, and who can push to what branch or tag - an important issue in
+ corporate environments. Other features include:
+ * access control by branch-name or by modified file/directory;
+ * per-developer "personal namespace" prefixes;
+ * simple but powerful configuration file syntax (with validation);
+ * config files (and authority for maintaining them) can be split;
+ * easy integration with gitweb;
+ * comprehensive logging;
+ * easy migration from gitosis.
Template: gitolite/gituser
Type: string
Default: gitolite
_Description: System user for gitolite:
Please enter the name for the system user which should be used by
gitolite. It will be created if necessary, and its home
directory will be used to store repositories.
Template: gitolite/gitdir
Type: string
Default: /var/lib/gitolite
_Description: Repository path:
Please enter the path in which the gitolite repositories should be stored.
This will be set as the system user's home directory.
Template: gitolite/adminkey
Type: string
_Description: Administrator's SSH key:
Please specify the key of the user that will administer the access
configuration of gitolite.
.
This can be either the SSH public key itself, or the path to a file
containing it. If it is blank, gitolite will be left unconfigured and
must be set up manually.
Source: gitolite
Section: vcs
Priority: optional
Maintainer: Gerfried Fuchs <rhonda@debian.at>
Build-Depends: quilt
Build-Depends-Indep: po-debconf
Standards-Version: 3.8.4
Homepage: http://github.com/sitaramc/gitolite
Vcs-Browser: http://git.deb.at/w/pkg/gitolite.git
Vcs-Git: git://git.deb.at/pkg/gitolite.git
Package: gitolite
Architecture: all
Depends: git (>= 1:1.7.0.4) | git-core (>= 1:1.6.2), perl (>= 5.6.0-16),
openssh-server | ssh-server, debconf (>= 0.5) | debconf-2.0, adduser
Suggests: git-daemon-run, gitweb
Description: SSH-based gatekeeper for git repositories
Gitolite is an SSH-based gatekeeper providing access control for a server that
hosts many git repositories. Without gitolite, each developer needing to push
to one of the repositories hosted would need a user account on the server;
gitolite replaces this with SSH public keys tied to a single user that hosts
all the repositories.
.
Gitolite can restrict who can read (clone/fetch) from or write (push) to a
repository, and who can push to what branch or tag - an important issue in
corporate environments. Other features include:
* access control by branch-name or by modified file/directory;
* per-developer "personal namespace" prefixes;
* simple but powerful configuration file syntax (with validation);
* config files (and authority for maintaining them) can be split;
* easy integration with gitweb;
* comprehensive logging;
* easy migration from gitosis.
Reply to: