git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kay Sievers <kay.sievers@vrfy.org>
To: Horst von Brand <vonbrand@inf.utfsm.cl>
Cc: Junio C Hamano <junkio@cox.net>,
	Linus Torvalds <torvalds@osdl.org>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: git binary directory?
Date: Sun, 6 Nov 2005 06:00:49 +0100	[thread overview]
Message-ID: <20051106050049.GA5910@vrfy.org> (raw)
In-Reply-To: <200511060312.jA63CUcv010887@inti.inf.utfsm.cl>

On Sun, Nov 06, 2005 at 12:12:30AM -0300, Horst von Brand wrote:
> Junio C Hamano <junkio@cox.net> wrote:
> > Linus Torvalds <torvalds@osdl.org> writes:
> > > Now, I happen to think that 2500+ files in /usr/bin is a bit much (ever 
> > > try to use the horrid gnome executable finder on it when you want to 
> > > convince firefox to use xpdf instead of that broken crap called "evince"? 
> > > Takes absolutely ages and is horrible).
> > >
> > > And git made it about 4% worse all on its own.
> 
> [...]
> 
> > Since we do not have enough clout to have /usr/bin/git/ and ask
> > the users to put that in their PATH like X11 does,
> 
> That is going away. No more /usr/X11R6/{bin,lib,man} junk.
> 
> >                                                    we need to
> > teach some of our commands that use other git commands to
> > prepend /usr/lib/git/ (or /usr/libexec/git)
> 
> AFAIU, /usr/libexec/git (or /usr/libexec/git-<version>) would be better.

Note that "libexec" is not LSB conform - whatever that means, but it
should probably not be used for new projects. It states: "Applications
may use a single subdirectory under /usr/lib."

Kay

  reply	other threads:[~2005-11-06  5:01 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-05 21:02 git binary directory? Linus Torvalds
2005-11-05 23:52 ` Linus Torvalds
2005-11-06  0:27   ` Linus Torvalds
2005-11-06  7:25     ` Junio C Hamano
2005-11-06  2:49 ` Junio C Hamano
2005-11-06  3:12   ` Horst von Brand
2005-11-06  5:00     ` Kay Sievers [this message]
2005-11-06  5:36       ` Junio C Hamano
2005-11-06  8:23         ` Petr Baudis
2005-11-06  8:33           ` Junio C Hamano
2005-11-06  8:28     ` Petr Baudis
2005-11-06  4:25   ` Linus Torvalds
2005-11-06  5:37     ` Junio C Hamano
2005-11-06 16:20       ` Linus Torvalds
2005-11-06 20:15         ` Junio C Hamano
2005-11-06 22:19           ` Petr Baudis
2005-11-07  0:08             ` Junio C Hamano
2005-11-07  0:43               ` Petr Baudis
2005-11-07  0:54                 ` Linus Torvalds
2005-11-07  9:45                   ` Petr Baudis
2005-11-07 17:27                   ` Junio C Hamano
2005-11-10  9:49                     ` Petr Baudis
2005-11-09 13:32                 ` Andreas Ericsson
     [not found] <436D2269.6090605@slamail.org>
2005-11-05 21:43 ` Yaacov Akiba Slama
2005-11-06  8:56   ` Ben Clifford
2005-11-06 13:13     ` Nikolai Weibull
2005-11-06 14:05       ` Johannes Schindelin
2005-11-06 15:03         ` Nikolai Weibull

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20051106050049.GA5910@vrfy.org \
    --to=kay.sievers@vrfy.org \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    --cc=torvalds@osdl.org \
    --cc=vonbrand@inf.utfsm.cl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).