From: Chris Wright <chrisw@osdl.org>
To: "Joshua T. Corbin" <jcorbin@wunjo.org>
Cc: Chris Wright <chrisw@osdl.org>, git@vger.kernel.org
Subject: Re: [PATCH] git-pasky debian dir
Date: Fri, 22 Apr 2005 11:45:51 -0700 [thread overview]
Message-ID: <20050422184551.GB5324@shell0.pdx.osdl.net> (raw)
In-Reply-To: <200504221400.11507.jcorbin@wunjo.org>
* Joshua T. Corbin (jcorbin@wunjo.org) wrote:
> On 22 April 2005 12:16, Chris Wright <chrisw@osdl.org> wrote:
> > This whole bit should be formalized.
> Agreed, hence why I did it as a package-build-time patch instead of changing
> directly in my repository.
>
> > Ideally, I'd like to do /usr/bin/git frontend, with all scripts
> > in /usr/libexec/git/.
> How standard is this '/usr/libexec'? I have no such directory on my Debian
> boxes. If /usr/share rubs you the wroung way, what of
> simply /usr/lib/git-pasky?
Hrm, it's not in FHS, but it's certainly in use on my install:
$ find /usr/libexec | wc -l
122
I don't care too much, I imagine distros wind up customizing this
anyway.
> > However, this requires something more than hardcoding paths.
> Definately, and it may not play well with the simpler method of installing to
> $HOME/bin. This was just a quick hack as not to pollute /usr/bin with files
> that aren't directly executed by the user.
Yup, that's why I dropped 'em in /usr/local/bin for now.
> > You get the idea ;-) I certainly see how it makes sense for a first
> > run to get it going. But this will need fixing upstream.
> This will all be moot when cogito goes the way of cg-* ;-)
Hrm...good point.
thanks,
-chris
--
Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net
prev parent reply other threads:[~2005-04-22 18:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-22 13:18 [PATCH] git-pasky debian dir Joshua T. Corbin
2005-04-22 16:16 ` Chris Wright
2005-04-22 18:00 ` Joshua T. Corbin
2005-04-22 18:45 ` Chris Wright [this message]
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=20050422184551.GB5324@shell0.pdx.osdl.net \
--to=chrisw@osdl.org \
--cc=git@vger.kernel.org \
--cc=jcorbin@wunjo.org \
/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).