* 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 - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.htmlReceived on Sat Apr 23 04:46:20 2005
This archive was generated by hypermail 2.1.8 : 2005-04-23 04:46:20 EST