From: Felipe Contreras <felipe.contreras@gmail.com>
To: Junio C Hamano <gitster@pobox.com>,
Felipe Contreras <felipe.contreras@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] completion: move out of contrib
Date: Wed, 07 May 2014 14:45:17 -0500 [thread overview]
Message-ID: <536a8d4dd798e_76ff7a52ec26@nysa.notmuch> (raw)
In-Reply-To: <xmqqppjpbicu.fsf@gitster.dls.corp.google.com>
Junio C Hamano wrote:
> Felipe Contreras <felipe.contreras@gmail.com> writes:
>
> > As an example of all the hacks needed by a real distribution package,
> > here's the stuff ArchLinux packagers have to do:
> >
> > # bash completion
> > mkdir -p "$pkgdir"/usr/share/bash-completion/completions/
> > install -m644 ./contrib/completion/git-completion.bash "$pkgdir"/usr/share/bash-completion/completions/git
> >...
> >
> > And here's what debian packagers have to do:
> >
> > # bash completion
> > install -d -m0755 '$(GIT)'/etc/bash_completion.d
> > install -m0644 contrib/completion/git-completion.bash \
> > '$(GIT)'/etc/bash_completion.d/git
> >...
> >
This is what the latest debian package does:
# bash completion
install -d -m0755 '$(GIT)'/usr/share/bash-completion/completions
install -m0644 contrib/completion/git-completion.bash \
'$(GIT)'/usr/share/bash-completion/completions/git
ln -s git '$(GIT)'/usr/share/bash-completion/completions/gitk
> > If our build system was sane, they wouldn't need so many hacks.
>
> I do not see how the above two examples lead to that conclusion.
> How would it help to blindly install to $(sharedir),
It is not blind, it is the location bash-completion uses *by default*,
and it's what most (all?) distributions use.
> or suggestion to use pkg-info when major distros do not even use one?
Which major distros do not ship with the pkg-config? It is part of
bash-completion (as it should be part of every decent shared softare
component), they all ship it.
Do you want me to go on a hunt and list all the distrubionts that ship
both?
/usr/share/bash-completion/completions/git
/usr/share/pkgconfig/bash-completion.pc
How many distributions would it take for you to accept the facts?
> I would understand if the saneness you seek were for distros to
> agree on where things should go, or at least agree on how to find
> out where things should go.
They all gree.
> I do not think we are there yet.
You are wrong.
--
Felipe Contreras
prev parent reply other threads:[~2014-05-07 19:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-03 0:36 [PATCH] completion: move out of contrib Felipe Contreras
2014-05-07 0:28 ` Junio C Hamano
2014-05-07 1:18 ` Felipe Contreras
2014-05-07 10:10 ` Felipe Contreras
2014-05-07 17:37 ` Junio C Hamano
2014-05-07 19:45 ` Felipe Contreras [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=536a8d4dd798e_76ff7a52ec26@nysa.notmuch \
--to=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).