move plasma tools to plasmate

[Sebastian Kügler]

Hey,

On Monday, August 27, 2012 10:17:21 Alex Fiestas wrote:
> > > Since we are adding "yet another" repo, our tools will be segregated
> > > across
> > > more repositories, making worse the already not ideal situation.
> > 
> > The idea is to consolidate all those development tools into one repo, not
> > the opposite. :)
> > 
> > For those building from Git, we can then add that repo to those built by
> > default to kdesrc-build.
> 
> My idea of consolidating is sending an email to plasma-devel/kde-
> devel/whatever to ask about opinions, see what we've got so far (kdesdk) and
> try to make use of it in an unified way.
> 
> Moving the tools to plasmate repo is a decision taken by (I don't know) in
> (I don't know where) and that's why it struck me at the first place. No
> doubt this was discussed but again it seems to me that we have failed again
> in the communication field.

Dude, no! :) We're discussing it right now. If we'd just gone ahead and made 
the changes, then yes, communication fail. But saying "we're failing to talk 
about this, while we are actually talking about it" is wrong. :P

> Plasmate only allows to create plasmoids javascript based afaik and it is
> desgined to do only that (which is cool). Imho it is waaaay far from being
> an sdk.

Plasmate is not a complete SDK for everything, sure. The point here is not so 
much Plasmate though, but where to put bits and pieces for Plasma development. 
If we rename Plasmate to Plasma SDK, it might be clearer, but really, the 
point is consolidating the tools in one place so the new developer doesn't 
have to go hunting down bits and pieces in X different places.

> Also, Plasmate (again afaik) is not done using kdevplatform, I have been
> told since day 1 that it will be at some point but apparently it is not. I
> don't know if kdevplatform is the solution but what I know is that we need
> to share stuff.

I don't think that matters at all here.

> > > Said that, I would prefer to move the tools to kdesdk since we already
> > > have
> > > that repository, but if it really helps you to move them to plasmate
> > > then
> > > go ahead, make things little worse won't be a deal breaker in this case.
> > 
> > BTW, wasn't the kdesdk SVN module split up? I'd personally rather not have
> > to build 10 repos to get all my development tools together.
> 
> Afaik it is still in SVN (http://websvn.kde.org/trunk/KDE/kdesdk/
> )

Well, parts of it are still there, but I think that's mostly due to nobody 
taking care of the transition. That SVN repo is going to die as soon as the 
last bit in there has been moved to git.

> Aaaah so much work to do and so little time :p I whish I could be one month
> working only on SDK, refactoring techbase etc :/

Agree, maybe we're still lacking the grand master plan how to structure our 
SDK, what's part of it and where to put these things?
-- 
sebas

http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9