86e9e88530Added git-remote-p2p-annex, which allows git pull and push to P2P networks provided by external commands. This is a refactor of git-remote-tor-annex, and should just work. Except possibly for quirks with the address parsing. I've checked that the address parsing basically works. One thing I don't understand is why git-remote-tor-annex removes "/*" from the end of the address. The git history does not provide any hints. So I didn't make git-remote-p2p-annex do the same. Maybe that is needed in some situation? But, a P2P address could contain "/", so removing it would be a problem. I can't see anything in gitremote-helpers(7) about why the url might get such a thing added to the end of it. My guess is that is not needed for tor either (but does no harm there since onion addresses never contain "/"). At this point, the implementation of generic P2P transports needs only remotedaemon support.
30 lines
822 B
Haskell
30 lines
822 B
Haskell
{- git-annex multicall binary
|
|
-
|
|
- Copyright 2024-2025 Joey Hess <id@joeyh.name>
|
|
-
|
|
- Licensed under the GNU AGPL version 3 or higher.
|
|
-}
|
|
|
|
module CmdLine.Multicall where
|
|
|
|
import qualified Data.Map as M
|
|
|
|
-- Commands besides git-annex that can be run by the multicall binary.
|
|
--
|
|
-- The reason git-annex itself is not included here is because the program
|
|
-- can be renamed to any other name than these and will behave the same as
|
|
-- git-annex.
|
|
data OtherMultiCallCommand
|
|
= GitAnnexShell
|
|
| GitRemoteAnnex
|
|
| GitRemoteP2PAnnex
|
|
| GitRemoteTorAnnex
|
|
|
|
otherMulticallCommands :: M.Map String OtherMultiCallCommand
|
|
otherMulticallCommands = M.fromList
|
|
[ ("git-annex-shell", GitAnnexShell)
|
|
, ("git-remote-annex", GitRemoteAnnex)
|
|
, ("git-remote-p2p-annex", GitRemoteP2PAnnex)
|
|
, ("git-remote-tor-annex", GitRemoteTorAnnex)
|
|
]
|
|
|