From: Felipe Contreras <felipe.contreras@gmail.com>
To: "Bagas Sanjaya" <bagasdotme@gmail.com>,
"Junio C Hamano" <gitster@pobox.com>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: Felipe Contreras <felipe.contreras@gmail.com>,
Jeff King <peff@peff.net>,
"brian m. carlson" <sandals@crustytoothpaste.net>,
Siavash <siavash.askari.nasr@gmail.com>,
git@vger.kernel.org
Subject: Re: Renaming "non-contrib" things out of contrib/* (was "Re: [Bug] git-credential-netrc.perl[...]")
Date: Tue, 25 May 2021 04:05:40 -0500 [thread overview]
Message-ID: <60acbde4621f1_2257a20819@natae.notmuch> (raw)
In-Reply-To: <8c08ee45-d7e4-b816-e883-a18dfa69fbc1@gmail.com>
Bagas Sanjaya wrote:
> On 25/05/21 13.51, Junio C Hamano wrote:
> > I think dispelling the conception by distro people must begin with
> > an update to contrib/README where it clearly says these are
> > "contributed software" that are not part of "Git". They are not
> > something we stand behind like what we have in the rest of the
> > source tree.
> >
> Archlinux packagers did remove contrib/ because they don't interest
> on it [1]:
Huh? The whole content of contrib/ is installed in /usr/share/git/ [1]
Some stuff like git-completion.bash is installed *twice*.
Once in `/usr/share/bash-completion/completions/git` and another in
`/usr/share/git/completion/git-completion.bash`.
> > Right now the Arch Linux's git package does this:
> >
> > find contrib/ -name '.gitignore' -delete
> > cp -a ./contrib/* "$pkgdir"/usr/share/git/
>
> > Also, the description there is rather stale. For example, the last
> > paragraph must go as its entirety. The ecosystem has expanded
> > thousand-fold since the document was written, and we no longer
> > encourage people to add new things to contrib/ directory at all. We
> > instead encourage them to write and sell their ware on their own
> > merit alone, without planning to "borrow" authority and gain undue
> > advantage over its competitors by being in the contrib/ area in our
> > tree.
> > .
> >
>
> So basically we should deprecate contrib/, and then after next few
> releases we proceed to remove it, right?
I tried that many years ago[2]. Didn't work.
[1] https://archlinux.org/packages/extra/x86_64/git/#filelink
[2] https://lore.kernel.org/git/1399662703-355-1-git-send-email-felipe.contreras@gmail.com/
--
Felipe Contreras
next prev parent reply other threads:[~2021-05-25 9:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-20 9:51 [Bug] git-credential-netrc.perl is not built and is not available in `exec-path` Siavash
2021-05-20 20:41 ` Jonathan Nieder
2021-05-21 10:26 ` Siavash
2021-05-21 1:55 ` brian m. carlson
2021-05-21 10:04 ` Jeff King
2021-05-21 22:27 ` brian m. carlson
2021-05-23 19:57 ` Jeff King
2021-05-24 3:01 ` Felipe Contreras
2021-05-24 10:05 ` Renaming "non-contrib" things out of contrib/* (was "Re: [Bug] git-credential-netrc.perl[...]") Ævar Arnfjörð Bjarmason
2021-05-24 17:21 ` Felipe Contreras
2021-05-24 23:18 ` Ævar Arnfjörð Bjarmason
2021-05-25 1:23 ` Felipe Contreras
2021-05-25 6:51 ` Junio C Hamano
2021-05-25 7:31 ` Bagas Sanjaya
2021-05-25 9:05 ` Felipe Contreras [this message]
2021-05-25 10:35 ` Felipe Contreras
2021-05-21 10:06 ` [Bug] git-credential-netrc.perl is not built and is not available in `exec-path` Jeff King
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=60acbde4621f1_2257a20819@natae.notmuch \
--to=felipe.contreras@gmail.com \
--cc=avarab@gmail.com \
--cc=bagasdotme@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
--cc=sandals@crustytoothpaste.net \
--cc=siavash.askari.nasr@gmail.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).