From: Felipe Contreras <felipe.contreras@gmail.com>
To: "Junio C Hamano" <gitster@pobox.com>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: Felipe Contreras <felipe.contreras@gmail.com>,
git@vger.kernel.org, Luke Shumaker <lukeshu@lukeshu.com>
Subject: Re: [PATCH 0/2] extra: new concept of extra components
Date: Wed, 16 Jun 2021 15:48:58 -0500 [thread overview]
Message-ID: <60ca63ba201b6_602720884@natae.notmuch> (raw)
In-Reply-To: <xmqqim2evdyx.fsf@gitster.g>
Junio C Hamano wrote:
> Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:
>
> > On Sun, Jun 13 2021, Felipe Contreras wrote:
> >
> >> This patch series introduces the concept of extra components. These are
> >> components which are not yet part of the core but are good enough for
> >> distributions to ship, and in fact, they already do.
> >
> > I like this direction.
>
> I do not mind change, but it is fuzzy to me what direction you are
> in favor of. Is the gist of the idea to split what is in contrib/
> into two bins, ones that are closer to "official" and others? If
> so, I see sort-of merit in such a distinction, but whom is this
> trying to help?
Everyone.
1. People who download the source code and want to install git in a
similar way to how distributions do it
2. Developers who have no idea what's good in contrib/
3. Distribution packagers who want to know what's good enough to be
distributed, and don't want to manually copy files (i.e. all
distribution packagers)
> Distros would rather see what they use unmoved, and would not care
> where those that they do not use move to, I would imagine.
That is not true.
Distributions do not want to decide where to place
`contrib/completion/git-prompt.sh`, they want the git project to decide.
Obviously it has to be under '/usr/share/', preferably
'/usr/share/$project' (i.e. not /usr/share/git-core), but other than
that they do not care.
> So I suspect that it would help them more if we kept the ones that are
> closer to "official" in contrib/ and moved the rest to a new
> hierarchy?
Sure, that would help, but they still would want an install-contrib target.
A distribution packager that is maintaining 20 packages (or more)
doesn't want to keep track where every single file of her every
single package goes. She just wants to do `make install` and be done
with it. Any package that requires to manually copy some files to the
destination is simply a hassle to maintain.
--
Felipe Contreras
next prev parent reply other threads:[~2021-06-16 20:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-14 4:34 [PATCH 0/2] extra: new concept of extra components Felipe Contreras
2021-06-14 4:34 ` [PATCH 1/2] completion: graduate out of contrib Felipe Contreras
2021-06-14 14:12 ` Ævar Arnfjörð Bjarmason
2021-06-16 20:09 ` Felipe Contreras
2021-06-14 4:34 ` [PATCH 2/2] git-new-workdir: " Felipe Contreras
2021-06-14 14:18 ` [PATCH 0/2] extra: new concept of extra components Ævar Arnfjörð Bjarmason
2021-06-16 0:40 ` Junio C Hamano
2021-06-16 20:48 ` Felipe Contreras [this message]
2021-06-16 20:28 ` Felipe Contreras
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=60ca63ba201b6_602720884@natae.notmuch \
--to=felipe.contreras@gmail.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=lukeshu@lukeshu.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).