Christoph Anton Mitterer <cales...@scientia.net> writes:
> Package: gitolite3
> Version: 2.3-1
BTW, this version is wrong.
> I've seen you've moved the config file to /etc in 3.6.3-2.
> Maybe one can continue this and make gitolite3 more FSH
> compliant.
>
> The obvious next thing would probably be to move ~git/.gitolite/logs/
> to /var/logs/gitolite3 (respectively symlink it) and perhaps to add
> proper logrotation config.
This is already easily configurable by the admin: see
http://gitolite.com/gitolite/gitolite.html#appendix-3-v3.6.1-syslog
At the moment I don't see an elegant way of changing defaults in
gitolite.rc; I'll discuss that with upstream.
> What I did there, personally, is that I basically created a clone of
> the admin repo in /etc, i.e. /etc/gitolite (well actually I've named
> it /etc/local/gitolite to avoid any future conflicts). Not sure if
> this seems like a proper way to go for the package, i.e. that it
> automatically creates a clone a /etc that the user may use.
In general I prefer to avoid divergence from upstream, unless there is a
contradiction with policy MUST. For me it also doesn't make sense to
force the day to day administration (editing of config, adding/deleting
user keys) to use root on the server. Having files in /etc/ editable by
non-root is also a bit strange (and what user should be able to edit
them?).
