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

List:       kde-release-team
Subject:    Re: KDE 4.7 Beta1 (4.6.80) tarballs uploaded (try#1)
From:       Alexander Neundorf <neundorf () kde ! org>
Date:       2011-05-22 9:22:42
Message-ID: 201105221122.42791.neundorf () kde ! org
[Download RAW message or body]

On Saturday 21 May 2011, Dirk Mueller wrote:
> On Saturday 21 May 2011, Eric Hameleers wrote:
> > The turn of events with KDE 4.7.x is most unfortunate. I noticed an
> > explosion of source tarballs.
> 
> Yes, I started to resemble the git layout in the tarballs, given that I had
> a pain in the ass of work to do with reverting the git splitting for the
> 4.6 branch releases. I'll attach them for reference, but those scripts are
> ugly. I'm not aware of a better solution though, unless we use git
> submodules or maintain those scripts in the SVN.

For kdesupport ( I guess it's the same issue there) previously I checked out 
one module and built it, now it's 10 or 15 different git repositories.
This is quite inconvinient.
Probably similar for kde e.g. kdegames etc.

So, what I'm doing right now for kdesupport is to create one CMakeLists.txt, 
which contains all the contained projects (automoc4, phonon, attica, akonadi, 
...) via the externalproject()-feature from CMake.
What it does, is it gets and updates all the sources from git, configures, 
builds and installs them.
So it feels almost like it did before.

It's mostly working already. But I'm not sure where to put that 
CMakeLists.txt, since there is no "kdesupport" anymore.

Interested in this ?
Where do you think should I put this ?

Alex
_______________________________________________
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team
[prev in list] [next in list] [prev in thread] [next in thread]