Pierre-Yves David <pierre-yves.david@octobus.net> [Fri, 02 Dec 2022 18:19:59 +0100] rev 49869
peer: pass the `path` object to `make_peer`
We don't do anything with it yet, but we can start implementing it for each peer
type starting now.
Pierre-Yves David <pierre-yves.david@octobus.net> [Fri, 02 Dec 2022 18:18:57 +0100] rev 49868
path: allow to copy a path while adjusting the url
This will be used by `scheme` in the next changesets.
Pierre-Yves David <pierre-yves.david@octobus.net> [Sat, 03 Dec 2022 00:19:23 +0100] rev 49867
peer: store the path object used to build a peer from a repo
This is the simplest case, we so starts with it.
Pierre-Yves David <pierre-yves.david@octobus.net> [Fri, 02 Dec 2022 17:41:44 +0100] rev 49866
peer: build a `path` object on the fly when needed
So now, we always have a `path` object around when building the peer
Pierre-Yves David <pierre-yves.david@octobus.net> [Sat, 03 Dec 2022 00:16:07 +0100] rev 49865
peer: have `repo.peer` take an optional `path` argument
We are ready to start to actually set the value now.
Pierre-Yves David <pierre-yves.david@octobus.net> [Sat, 03 Dec 2022 00:13:50 +0100] rev 49864
peer: add a `path` attribute to peer
It will start being set in the coming changesets.
Pierre-Yves David <pierre-yves.david@octobus.net> [Sat, 03 Dec 2022 00:00:41 +0100] rev 49863
peer: have a common constructor and use it
For now it does not do much, but we will extend it to also store a path object
soon.