<div dir="ltr"><div>For Plasma all the tars have the same names as the git repos.</div><div><br></div><div>Jonathan</div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, 23 Aug 2019 at 15:13, Harald Sitter <<a href="mailto:sitter@kde.org">sitter@kde.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Yo!<br>
<br>
What's our stance on tar names different from the repo names?<br>
<br>
For simplicity's sake I would argue it should not ever happen, but are<br>
there practical reasons where we simply have to have it (other than<br>
for legacy naming reasons)?<br>
<br>
And if we do have a need for this, should we maybe encode the tarname<br>
in our repo-metadata json if it is different from the repo basename?<br>
<br>
Currently we don't really have the name map codified anywhere, which<br>
is a bit annoying to me because for legacy reasons phonon-vlc.git is<br>
actually released as phonon-backend-vlc but since that isn't codified<br>
in our metadata releaseme doesn't know that, and neither does neon's<br>
tooling (to map stuff the other way for git-master builds).<br>
<br>
Thoughts?<br>
<br>
HS<br>
</blockquote></div>