Re: If you would write git from scratch now, what would you change?
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Nov 26, 2007, 21:47 UTC
- Message-ID
- <7v3ausfzmh.fsf@gitster.siamese.dyndns.org>
- In-Reply-To
- <alpine.LFD.0.99999.0711261631170.9605@xanadu.home>
Nicolas Pitre <nico@cam.org> writes:
Show 22 quoted lines
> On Mon, 26 Nov 2007, Junio C Hamano wrote: > >> Wincent Colaiuta <win@wincent.com> writes: >> >> > For the benefit of newcomers, I just wish the plumbing was kept a >> > little bit out of sight. You know, porcelain in /usr/bin and plumbing >> > in /usr/libexec or other such place. >> > >> > It's fine once you've learnt your workflows and know the 10 or 15 Git >> > tools that you'll be using day-to-day; but for people who are just >> > starting off this can be a little bit intimidating: >> > >> > $ git-<tab> >> > Display all 146 possibilities? (y or n) >> >> I'd agree to that but I've always considered this an issue for distros. >> We've supported an ability for them to specify a gitexecdir separate >> from /usr/bin in our Makefile for almost two years. > > Would probably be a good thing to start enforcing that by default. It's > easier to follow such policies when they're coordinated from the project > origin.
Not really. The project origin ships the Makefile to install under $HOME, but I do not see any distros following that.