On Sunday 21 August 2011, Nicolas Alvarez wrote:
> Aaron J. Seigo wrote:
> > On Saturday, August 20, 2011 16:48:09 Raphael Kubo da Costa wrote:
> >> For now, I have created a scratch git repository with the files which
> >> used to be in the top-level kdeutils directory in SVN, so you can just
> >>
On Sunday 21 August 2011, Aaron J. Seigo wrote:
> On Saturday, August 20, 2011 16:48:09 Raphael Kubo da Costa wrote:
> > For now, I have created a scratch git repository with the files which
> > used to be in the top-level kdeutils directory in SVN, so you can just
> > use the CMakeLists.txt there
On Sunday, August 21, 2011 00:13:25 Nicolas Alvarez wrote:
> As I said in another thread: Superbuild is unrelated and orthogonal to
> the ability of the kdeutils buildsystem to allow building both as
> standalone apps and as a single module.
see my reply in that other thread as to what superbuild
Aaron J. Seigo wrote:
> On Saturday, August 20, 2011 16:48:09 Raphael Kubo da Costa wrote:
>> For now, I have created a scratch git repository with the files which
>> used to be in the top-level kdeutils directory in SVN, so you can just
>> use the CMakeLists.txt there to build everything (there ar
On Saturday, August 20, 2011 16:48:09 Raphael Kubo da Costa wrote:
> For now, I have created a scratch git repository with the files which used
> to be in the top-level kdeutils directory in SVN, so you can just use the
> CMakeLists.txt there to build everything (there are no inter-repository
> dep
Hello there,
kdeutils has (mostly) finished its migration to git. SVN now only holds
MOVED_TO_GIT files which point to the git repositories.
Each application (ark, filelight, kcalc, kcharselect, kfloppy, kgpg,
kremotecontrol, ktimer, kwallet, printer-applet, superkaramba, sweeper)
has its own git