[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-release-team
Subject:    Re: tar names vs. repo names
From:       Jonathan Riddell <jr () jriddell ! org>
Date:       2019-08-26 9:30:58
Message-ID: CANX=XXP3idwPjZiXPNF7WY=JZiWQ3oi7=9Vs6+ECwkzHaZoTWQ () mail ! gmail ! com
[Download RAW message or body]

For Plasma all the tars have the same names as the git repos.

Jonathan


On Fri, 23 Aug 2019 at 15:13, Harald Sitter <sitter@kde.org> 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
>

[Attachment #3 (text/html)]

<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 &lt;<a href="mailto:sitter@kde.org">sitter@kde.org</a>&gt; \
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&#39;s our stance on tar names different from the repo names?<br>
<br>
For simplicity&#39;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&#39;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&#39;t codified<br>
in our metadata releaseme doesn&#39;t know that, and neither does neon&#39;s<br>
tooling (to map stuff the other way for git-master builds).<br>
<br>
Thoughts?<br>
<br>
HS<br>
</blockquote></div>



[prev in list] [next in list] [prev in thread] [next in thread]