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

List:       kde-panel-devel
Subject:    Re: Proposal regarding plasmate's release
From:       David Edmundson <david () davidedmundson ! co ! uk>
Date:       2015-04-03 18:41:47
Message-ID: CAGeFrHCAh9VUKM9qVEijOaw1Xag8BaD_9-vTjss5LFnmj4qLgg () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


On Fri, Apr 3, 2015 at 8:10 PM, Jonathan Riddell <jr@jriddell.org> wrote:

> On Fri, Apr 03, 2015 at 08:52:09PM +0300, Antonis Tsiapaliokas wrote:
> > On Fri, Apr 03, 2015 at 06:08:52PM +0200, David Edmundson wrote:
> > > Can it go under kde/workspace if in future it will depend on something
> in
> > > extragear?
> > >
> > > I still support doing the rest, and making / release.. I'm just not
> sure we
> > > can do the move and release it with plasma.
> >
> > At the moment the only application inside from the Plasmate repo
> > which depends on extragear is Plasmate (the application), and it depends
> on the
> > Kdevplatform. The rest of the applications doesn't depend on extragear.
> >
> > Plasmate (the application) is currently being disabled from building by
> default.
> > So the Plasmate repo doesn't need something from extragear in order to
> build.
> >
> > In the feature Plasmate (the application) will be build as an optional
> depedency
> > only if the Kdevplatform is being present.
> >
> > So kde/workspace is building first from the kdesrc-build, so if we move
> the Plasmate
> > repo there, Plasmate (the application) it will never get build.
> > It will require a rebuild.
>
> I don't have a problem with it depending on stuff in extragear as we
> depend on many external items.  As long as that stuff we depend on in
> extragear doesn't depend on stuff in plasma.


What happens when kdevplatform releases an update with an API break?
You'll want  to release a new Plasmate. It being optional doesn't change
that.


>
> Jonathan
> _______________________________________________
> Plasma-devel mailing list
> Plasma-devel@kde.org
> https://mail.kde.org/mailman/listinfo/plasma-devel
>

[Attachment #5 (text/html)]

<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Apr \
3, 2015 at 8:10 PM, Jonathan Riddell <span dir="ltr">&lt;<a \
href="mailto:jr@jriddell.org" target="_blank">jr@jriddell.org</a>&gt;</span> \
wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span \
class="">On Fri, Apr 03, 2015 at 08:52:09PM +0300, Antonis Tsiapaliokas wrote:<br> \
&gt; On Fri, Apr 03, 2015 at 06:08:52PM +0200, David Edmundson wrote:<br> &gt; &gt; \
Can it go under kde/workspace if in future it will depend on something in<br> &gt; \
&gt; extragear?<br> &gt; &gt;<br>
&gt; &gt; I still support doing the rest, and making / release.. I&#39;m just not \
sure we<br> &gt; &gt; can do the move and release it with plasma.<br>
&gt;<br>
&gt; At the moment the only application inside from the Plasmate repo<br>
&gt; which depends on extragear is Plasmate (the application), and it depends on \
the<br> &gt; Kdevplatform. The rest of the applications doesn&#39;t depend on \
extragear.<br> &gt;<br>
&gt; Plasmate (the application) is currently being disabled from building by \
default.<br> &gt; So the Plasmate repo doesn&#39;t need something from extragear in \
order to build.<br> &gt;<br>
&gt; In the feature Plasmate (the application) will be build as an optional \
depedency<br> &gt; only if the Kdevplatform is being present.<br>
&gt;<br>
&gt; So kde/workspace is building first from the kdesrc-build, so if we move the \
Plasmate<br> &gt; repo there, Plasmate (the application) it will never get build.<br>
&gt; It will require a rebuild.<br>
<br>
</span>I don&#39;t have a problem with it depending on stuff in extragear as we<br>
depend on many external items.   As long as that stuff we depend on in<br>
extragear doesn&#39;t depend on stuff in plasma.  \
</blockquote><div><br></div><div>What happens when kdevplatform releases an update \
with an API break?  <br></div><div>You&#39;ll want   to release a new Plasmate. It \
being optional doesn&#39;t change that.</div><div>  <br></div><blockquote \
class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
 <span class=""><font color="#888888"><br>
Jonathan<br>
</font></span><div class=""><div \
class="h5">_______________________________________________<br> Plasma-devel mailing \
list<br> <a href="mailto:Plasma-devel@kde.org">Plasma-devel@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/plasma-devel" \
target="_blank">https://mail.kde.org/mailman/listinfo/plasma-devel</a><br> \
</div></div></blockquote></div><br></div></div>


[Attachment #6 (text/plain)]

_______________________________________________
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel


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

Configure | About | News | Add a list | Sponsored by KoreLogic