diff options
author | Boris Kolpackov <boris@codesynthesis.com> | 2016-09-24 21:17:59 +0200 |
---|---|---|
committer | Boris Kolpackov <boris@codesynthesis.com> | 2016-09-24 21:17:59 +0200 |
commit | fd348fe1be0fc4772d1ad07efa255b5b739f8fd2 (patch) | |
tree | 31ebb7ec44a256608104b94e49b26974441081d4 | |
parent | dd1aa8922a5e1505b17c46ab120f11b5979a2b66 (diff) |
Add idea: Support for git:// as repository protocol
-rw-r--r-- | bpkg/git-repository-protocol | 18 |
1 files changed, 18 insertions, 0 deletions
diff --git a/bpkg/git-repository-protocol b/bpkg/git-repository-protocol new file mode 100644 index 0000000..902ff1f --- /dev/null +++ b/bpkg/git-repository-protocol @@ -0,0 +1,18 @@ +? Support for git:// as repository protocol [idea] + +We are thinking about fetching packages directly from git repositories but it +may also make sense to store entire repositories in git. + +The main advantage will probably be the ease of use (i.e., just push your +stuff to github, no need to run HTTP server). But can't we already access +things (perhaps less efficiently) via git's HTTP protocol, i.e., isn't the +repository just a bunch of files via HTTP? + +The main disadvantage will be the need to store generated manifests in the +repository, which will probably become binary (compressed). + +What also could be useful is the ability to treat a group of git repositories +(and specific branch) as a repository somehow (e.g., for bbot dependency +resolution). + +See also git-package-protocol. |