[rb-general] SOURCE_PREFIX_MAP format specification proposals

[Daniel Shahaf]

Ian Jackson wrote on Wed, Jan 18, 2017 at 11:27:56 +0000:
> Daniel Shahaf writes ("Re: [rb-general] SOURCE_PREFIX_MAP format specification proposals"):
> > Couldn't we just, right now, say "'SOURCE_PREFIX_MAP v0' uses the
> > encoding of $PATH", so consumers/producers have something concrete to
> > play with?  We could subsequently release a v1 that adds supports for
> > colons, but as they say, "release early and often".
> 
> Not unless you also, in advance, forbid certain other characters.
> Otherwise there is no room for expansion.

Good point.  I was imagining we'd either name the envvar
SOURCE_PREFIX_MAP_v0 or embed the version number in the value
(SOURCE_PREFIX_MAP="v0:..."), for forwards compatibility.