Re: Why /var/cache/git?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Oct 25, 2010 at 08:24:47AM -0700, J.H. wrote:
> On 10/25/2010 03:30 AM, Bron Gondwana wrote:
> > (resent - correct address for git list!)
> > 
> > (Gerrit: you're CC'd as the attribution in README.Debian
> >  which in the one place I can see /var/cache/git mentioned
> >  in the docs - without a justification for why it was
> >  chosen...)
> 
> Couple of quick points:
> 
> $ grep -Ri "/var/git\|\/var\/git" *
> Documentation/git-cvsserver.txt:     export
> CVSROOT=:ext:user@server:/var/git/project.git
> 
> gitweb/README:    RewriteRule ^/var(/|/gitweb.cgi)?$	
> /cgi-bin/gitweb.cgi [QSA,E=GITWEB_PROJECTROOT:/var/git/,L,PT]
> 
> gitweb/README:Second, repositories found in /pub/scm/ and /var/git/ will
> be accesible
> 
> Are the only 3 instances where this is mentioned.  Looking at those
> quick it was probably chosen based on the fact that it's a location that
> likely exists on most machines.  Or just for explanatory reasons like
> /example/dir/project.git could be used.

I have no problem with /var/git - it's /var/cache/git that worries
me, since the FHS quite clearly says that blowing away /var/cache/*
is not a problem.  It makes sense to back up /var/lib/ on any machine,
since that's somewhere that contains application data.  We already
back up a few things from /var/lib (like /var/lib/svn for example,
at least until we finish this switchover!)
 
Bron.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]