# subgit mit Homebrew Cask installieren Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für subgit in AI-Agent-Workflows. ## Installation ```sh sudo av install cask:subgit ``` Weitere Installationsbefehle: ### macOS - Homebrew Cask (100%): ```sh brew install --cask subgit ``` Evidenz: local Homebrew cask metadata ## Paketfakten - **Paketschlüssel:** cask:subgit - **Paketmanager:** Homebrew Cask - **Paketmanager-Seite:** - **Version:** 3.3.18 - **Quellzusammenfassung:** Convert SVN repositories to Git - **Homepage:** - **Upstream-Dokumentation:** - **Quellarchiv:** - **Generiert:** 2026-08-04T22:13:35+00:00 ## Executables - subgit (Binärdatei) - subgit (Alias) ## Installationsverhalten - Post-install-Hook: nicht definiert - Einschränkungen: subgit requires Java 7+. You can install the latest version with: brew install --cask temurin - Bottle: nicht verfügbar ## Version und Aktualität - Seite generiert: 2026-08-04 - Manager-Version: 3.3.18 - lokale Daten: OK - Upstream-Repository: https://subgit.com/ - Info: No package-manager update timestamp was available. - Info: Release/tag comparison is only available for GitHub repositories. ## Projektgeschichte und Nutzung SubGit is a TMate Software tool for converting and synchronizing Subversion repositories with Git. The official documentation describes both one-time SVN-to-Git import and Git/SVN mirror workflows where pushes to Git are translated to SVN and SVN commits are translated back to Git. ### Projektgeschichte The documentation says SubGit was developed from the beginning as an alternative to git-svn, aimed at resolving many git-svn limitations. Its release notes cover version history since 1.0 and show the product evolving around repository translation, mirror modes, Git hosting integrations, shared daemon operation, and SVNKit/JGit updates. ### Adoptionsgeschichte SubGit is packaged as a Homebrew cask in the input facts and distributed by the vendor as a downloadable zip. Official docs include guides for GitLab, GitHub, Gerrit, Bitbucket Server, and Gogs, reflecting adoption around organizations moving from Subversion to Git while keeping legacy SVN workflows alive. ### Wie es verwendet wird Common CLI usage starts with `subgit configure` to create or configure a bare Git mirror, editing `repos.git/subgit/config` and author mappings, then running `subgit install` for ongoing mirroring or `subgit import` for one-time import. The quick how-to notes that SVN credentials may come from the user's `~/.subversion` cache. ### Warum Paket-Nerds sich dafür interessieren SubGit is relevant to package and release engineers because it sits at the boundary between two version-control histories. It exists for teams that cannot simply abandon SVN, so packagers care about repeatable install locations, Java requirements, license limits, credential handling, Git hosting integrations, and long-running daemon behavior. ### Zeitleiste - 2012: Vendor site footer copyright begins at 2012, matching SubGit's long-running commercial distribution era. - 2.0.0: Release notes introduced remote Subversion repository support and one-shot import from SVN to Git. - 3.0.0: Release notes introduced automated layout detection, out-of-sync recovery, shared background daemon support, script-based author mapping, and Git credential-helper support. - 3.3.18: Release notes list dependency updates for known vulnerabilities and shared daemon scheduler improvements. ### Related projects - The official docs compare SubGit with git-svn and document integrations with GitLab, GitHub, Gerrit, Bitbucket Server, Gogs, SVNKit, JGit, and Subversion credential storage. ### Quellen - - - - input source_facts.package-manager - input source_facts.source-archive ## Sicherheitshinweise Für subgit wurde kein passendes lokales Secret-Handling-Manifest gefunden. Paketmetadaten bleiben hier veröffentlicht, damit künftige Abdeckung eine stabile Paket-URL hat. ## Configuration and credential file locations These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval. ## Configuration files - Unix: /subgit/config, /conf/subgit.conf ## Credential files - Unix: /subgit/passwd, /subgit/config, ~/.subversion ## Details aus der Quelldatenbank - **Source Database:** Homebrew cask API - **Tap:** homebrew/cask - **Full Token:** subgit - **Names:** SubGit - **Artifacts:** Binary: 1, Target: 1, Zap: 1 - **Deprecated:** no - **Disabled:** no ## Andere Paketmanager-Einträge - Nix - subgit: normalized package name match | nixpkgs package indexes: pkgs/by-name/su/subgit/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 ## Verwandte Links - [Homebrew Cask packages](https://pkg.so/de/homebrew-cask-packages/) - Generated from Homebrew Cask package-manager metadata. - [Homebrew Cask binaries](https://pkg.so/de/homebrew-cask-binaries/) - Cask artifact metadata includes a binary. ## Combined YAML source View the package source record on GitHub. [combined/subgit.yml](https://github.com/mxcl/pkgdb/blob/main/combined/subgit.yml) ## Quellen - pkg.so package database - package-page enrichment - curated configuration and credential file locations - curated package history - package version freshness - pkgdb category and tag curation - package relationship graph - external package-manager database matches - cross-ecosystem install command graph