[okular/4.6] /: bump version to 0.12.5
Alexander Neundorf
neundorf at kde.org
Sun Jul 3 18:32:06 CEST 2011
On Sunday 03 July 2011, Albert Astals Cid wrote:
> A Saturday, July 02, 2011, Alexander Neundorf va escriure:
> > On Saturday 02 July 2011, Stephen Kelly wrote:
> > > Albert Astals Cid wrote:
> > > > A Saturday, July 02, 2011, Max Brazhnikov va escriure:
> > > >> On Sat, 2 Jul 2011 14:22:57 +0200, Dirk Mueller wrote:
> > > >> > On Thursday 30 June 2011, Pino Toscano wrote:
> > > >> > > Git commit 5ad1dd2761a26acdd2576c6451356fec856d5793 by Pino
> > > >> > > Toscano. Committed on 30/06/2011 at 23:52.
> > > >> > > Pushed by pino into branch '4.6'.
> > > >> > >
> > > >> > > bump version to 0.12.5
> > > >> >
> > > >> > Hi,
> > > >> >
> > > >> > I recreated kdegraphics tarball to include the right version of
> > > >> > okular:
> > > >> >
> > > >> > 9054b67c661847e7b41c57a19492ade8
> > > >> > sources/kdegraphics-4.6.5.tar.bz2
> > > >>
> > > >> kdegraphics has circular dependency on itself, namely mobipocket
> > > >> depends
> > > >
> > > >> on okular. At the first run:
> > > > Anyone knows where the CMakeLists.txt for kdegraphics itself comes
> > > > from? Obviously it does not come from kde:kdegraphics repo (since
> > > > this one is broken and does not even know about the existance of the
> > > > mobipocket "folder"). But then again since we do not have access to
> > > > the tarballs it's just speculating for the fun of it.
> > >
> > > It's in the superbuild repository.
> > >
> > > git clone kde:superbuild
> >
> > ...but if the one from superbuild is used, Mobipocket should find Okular.
> > Doesn't it ?
>
> No idea, how is one supposed to use the superbuild thing to get the 4.6
> tarballs like Dirk did?
The currently existing documentation is here:
https://projects.kde.org/projects/kde/superbuild
I don't know whether something changed in the structure between 4.6 and 4.7,
but basically:
git clone superbuild, this brings a CMakeLists.txt for kdegraphics.
Then run cmake on it, and then build "make UpdateAll", which just fetches the
sources. Then "make package", which creates a source package from these
sources including a top-level CMakeLists.txt.
This source package should be buildable everywhere.
Alex
More information about the Kde-buildsystem
mailing list