On 8/23/19 8:12 AM, Harald Sitter wrote:
Yo!
What's our stance on tar names different from the repo names?
For simplicity's sake I would argue it should not ever happen, but are
there practical reasons where we simply have to have it (other than
for legacy naming reasons)?
And if we do have a need for this, should we maybe encode the tarname
in our repo-metadata json if it is different from the repo basename?
Currently we don't really have the name map codified anywhere, which
is a bit annoying to me because for legacy reasons phonon-vlc.git is
actually released as phonon-backend-vlc but since that isn't codified
in our metadata releaseme doesn't know that, and neither does neon's
tooling (to map stuff the other way for git-master builds).
Thoughts?
HS
Personally I'm with you and believe a 1:1 mapping of technical names in
circumstances like this will simplify everything and probably robustify
various pieces of release-related code too.
Nate
