Re: Plan of action for source mirroring (client-side)

[Jonathan Maw <jonathan maw codethink co uk>]

On 2018-05-15 15:29, Jonathan Maw wrote:
> Hi,

[snip]

> * When fetching from buildstream-generated mirrors, it will have the
> format
> {URL}/sources/{source_kind}/{URL_directory_name}/{mirror_number}
>   where {URL} is the URL of the buildstream mirror generated via 
> config,
>   {source_kind} is the kind of the source (as specified in the yaml's
> "kind" field),
>   {URL_directory_name} is the URL specified for the source, mangled
> into a valid name for a directory (e.g. git://github.com becomes
> git___github_com),
>   {mirror_number} as a number starting from 0, and incrementing every
> time fetching/tracking returns a RefNotFoundError instead of a general
> SourceError.

On reflection, I am less certain about the format
"{URL}/sources/{source_kind}/{URL_directory_name}/{mirror_number}".
When cached locally, the path component represented as "{URL}/sources" 
is the configuration field "sourcedir".
Given there's nothing special about "sources", I think it prudent not to 
automatically include it.

Ta,

Jonathan