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

List:       kde-release-team
Subject:    Re: tar names vs. repo names
From:       David Faure <faure () kde ! org>
Date:       2019-08-28 7:24:05
Message-ID: 5530861.lOV4Wx5bFT () asterixp50
[Download RAW message or body]

For Frameworks too.

On lundi 26 août 2019 11:30:58 CEST Jonathan Riddell wrote:
> 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


-- 
David Faure, faure@kde.org, http://www.davidfaure.fr
Working on KDE Frameworks 5



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