From: Kyohei Kadota <email@example.com> To: "brian m. carlson" <firstname.lastname@example.org>, "KADOTA, Kyohei via GitGitGadget" <email@example.com>, firstname.lastname@example.org, Junio C Hamano <email@example.com> Subject: Re: [PATCH 0/6] Port git to Plan 9 Date: Sun, 4 Aug 2019 11:22:58 +0900 [thread overview] Message-ID: <CAFMepcm6QVH+5H6on2hoWiMXd=Zoyi5MYP1GAt0WwixZN9oE_Q@mail.gmail.com> (raw) In-Reply-To: <20190804003816.GE118825@genre.crustytoothpaste.net> 2019-08-04(Sun) 9:38 brian m. carlson <firstname.lastname@example.org>: > > On 2019-08-03 at 23:52:08, KADOTA, Kyohei via GitGitGadget wrote: > > I ported git, and git subcommands only written in C to Plan 9. This pull > > request contains patches for existing codes, and new files to build git in > > Plan 9. > > > > All build options such as NO_PERL are not supported yet, and also some git > > subcommands written not in C is not available yet. But git can synchronize > > to remote repository with git pull and git push via HTTPS. > > > > This pull request don't contain a part of Git toolchain for example > > git-credential-store, etc. So I'm going to port other parts of Git toolchain > > too in the future. > > This series seems to build a whole new build system that uses Plan 9 > tools. Typically the way ports to non-POSIX platforms (such as Windows) > have been handled is that the Unix tools, including GNU make, have been > ported to those platforms, and the POSIX (or POSIX-ish) environment used > there. > > I'm concerned that by introducing a whole bunch of new, Plan 9-specific > build code, we're going to have it fall behind with features or bug > fixes, because none of the main developers test on Plan 9, and most > contributors will not have the Plan 9 skills or systems to maintain the > code. > > In addition, the editor used by git commit and other commands invokes > "sh", but you've set this to "rc". That's completely different from the > way that all other environments work, and it means that Git on Plan 9 > operates in a totally different, incompatible way there. We also use a > POSIX shell for the testsuite, and we rely on it quite heavily. rc is > not going to cut it there. > > Plan 9 has a POSIX environment, and I think it might be a better idea to > require that as a condition for building and running Git. It will likely > be a lot easier, at least. > -- > brian m. carlson: Houston, Texas, US > OpenPGP: https://keybase.io/bk2204 I think it is possible to replace rc with ape/sh, ape/sh is POSIX shell in Plan 9. However Plan 9 don't have recent versions of Unix tools, such as gcc, g++, autotools, gmake or perl, so it is VERY hard to use Makefile instead of mkfile.
next prev parent reply other threads:[~2019-08-04 2:42 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-08-03 23:52 KADOTA, Kyohei via GitGitGadget 2019-08-03 23:52 ` [PATCH 1/6] Change HOME, PATH, and .gitconfig paths to be customizable lufia via GitGitGadget 2019-08-03 23:52 ` [PATCH 2/6] Fix C syntactic errors for the Plan 9 C compiler lufia via GitGitGadget 2019-08-03 23:52 ` [PATCH 3/6] GIT-VERSION-GEN: Use sed instead of expr lufia via GitGitGadget 2019-08-05 22:37 ` Junio C Hamano 2019-08-03 23:52 ` [PATCH 4/6] Port generate-cmdline.sh to rc lufia via GitGitGadget 2019-08-03 23:52 ` [PATCH 5/6] Add plan9/wrap.c lufia via GitGitGadget 2019-08-04 0:03 ` brian m. carlson 2019-08-04 1:26 ` Kyohei Kadota 2019-08-03 23:52 ` [PATCH 6/6] Add mkfile to build git and subcommands for Plan 9 lufia via GitGitGadget 2019-08-04 0:38 ` [PATCH 0/6] Port git to " brian m. carlson 2019-08-04 2:22 ` Kyohei Kadota [this message] 2019-08-04 20:22 ` Jonathan Nieder 2019-08-27 13:46 ` [PATCH v2 0/3] " KADOTA, Kyohei via GitGitGadget 2019-08-27 13:46 ` [PATCH v2 1/3] Change HOME, PATH, and .gitconfig paths to be customizable lufia via GitGitGadget 2019-08-27 13:46 ` [PATCH v2 2/3] Fix C syntactic errors for the Plan 9 C compiler lufia via GitGitGadget 2019-08-27 13:46 ` [PATCH v2 3/3] Support Plan 9 dialect lufia via GitGitGadget
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='CAFMepcm6QVH+5H6on2hoWiMXd=Zoyi5MYP1GAt0WwixZN9oE_Q@mail.gmail.com' \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [PATCH 0/6] Port git to Plan 9' \ /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
Code repositories for project(s) associated with this 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).