Re: Embedding Git Command Line
- From
Johannes Schindelin <johannes.schindelin@gmx.de>
- Date
- May 18, 2024, 19:50 UTC
- Message-ID
- <224aff4c-facc-76cd-94c1-8b40f18c0d40@gmx.de>
- In-Reply-To
- <20240516181738.g7iw6rfqvjfucoiw@carbon>
Hi,
On Thu, 16 May 2024, Konstantin Khomoutov wrote:
Show 19 quoted lines
> On Thu, May 16, 2024 at 01:04:35PM +0100, Kevin Gale wrote: > > > We are looking to embed version control features into our commercially > > licensed proprietary product. > > > > We haven’t made a decision on which technology yet but Git would be a > > popular choice. > [...] > > While only tangentially related, I'd point out that if your product is going > to actually _bundle_ Git, then be prepared that it has quite a hefty set > of dependencies, so unless you're going to rely on the target OS to provide > them (which is, as I understand it, a no-go on Windows) you might be required > to invest considerable effort into that endaevor. > > On the other hand, if it's not a shrink-wrap product but rather something > enterprise-y (kind of software usually installed by a dedicated technician - > as opposed to being downloaded and click-through installing by a layperson), > you might just use what Git for Windows ships, I suppose.
Git for Windows offers MinGit (for full details, see https://github.com/git-for-windows/git/wiki/MinGit), which is a subset of Git for Windows intended to be bundled by 3rd-party applications. That's what Visual Studio and GitHub Desktop do.
Ciao, Johannes