Control: notfound -1 2.3-1
Control: found -1 3.6.4-1

On Mon, 2015-12-07 at 09:04 -0400, David Bremner wrote:
> Package: gitolite3
> > Version: 2.3-1
> 
> BTW, this version is wrong.
hmm weird... no idea how I got that in ^^



> > 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-sys
> log
Sure.. the point is just, Debian should do that perhaps out-of-the box.


> At the moment I don't see an elegant way of changing defaults in
> gitolite.rc; I'll discuss that with upstream.
Maybe simply symlink the logs dir?


> 
> > 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.
Well I guess we're at a corner case here: The policy, IIRC, says that
FHS must be followed (more or less)... FHS in turn says: configuration
goes to /etc.
Obviously gitolite has two kinds of config:
1) the canonical config which can be anywhere in any number of admin
repo clones
2) the current state of the config (which IMHO should really be in
/var, as it is).


>  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?).
Sure... one could also simply say, that gitolite doesn't have that
classic in-/etc  as in (1) above... and that we keep things here as is,
and define no standard location which the user may not use anyway.


Cheers,
Chris.

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to