This reverts commit 089edc6a73.
Although auto-grouping is a nice easy way to get approximately right
dependency ordering, it doesn't work in all situations.
The "Best" thing would be to only sort within kde-project modules (as
expanded) but for now just back out this commit so I don't break
customized rc-files.
BUG:297847
Valery Yundin has kindly submitted a patch (including documentation!)
resurrecting the old "use-stable-kde" option to allow for defaulting
kde-projects modules to the stable branch (if defined for that module).
This should track with changes to the stable branch as defined, so it
would be a good way to track the "not quite bleeding-edge" of
development.
A hearty thanks to Valery for making up a patch and then adapting it to
make use of the old use-stable-kde option.
BUG:297357
FIXED-IN:1.15
This occurs before dependency resolution (so that the dependency metadata is
still "preferred"), and is a simplistic dependency sorting technique.
This prevents dependency-data metadata from having to become insanely
complicated to ensure that each module depends on kdelibs (since kdelibs can't
simply be special-cased to be "dependency #2" as it has a lot of dependencies
itself on kdesupport/ modules like automoc.
So, we instead group modules after dependency resolution into:
qt (right now, just the projects.kde.org one, not any generic Qt)
kdesupport/*
kdelibs
projects.kde.org modules not already determined
other modules
It is possible to override the tier you end up at by setting the
"ordering-tier" option for that module to an integer.
This commit should make the 'prefix' option expand this variable to the
module's name, so one can easily install each module into a different
directory.
Reviewed-by: mpyne
Now you can specify the private key to be passed to your SSH agent if
you forgot to run that before running kdesrc-build.
Proof-of-concept patch graciously provided by Ralf Jung.
BUG:284071
FIXED-IN:1.14.2
This doesn't so much actively search for things to delete. Instead it's
a required permission from the user to remove source directories (which
is similar to the remove-after-install option).
Right now this will only be used when trying to clone a git module and
the destination source directory already exists somehow, which has
happened for a lot of 1.14 early adopters due to old kde-baseapps
checkouts having a kate or konsole directory that conflict with where
kdesrc-build wants to put the current kate/konsole directories.
asciidoc was a nice start, but modifying the generated XML is not too
bad (and must be done to comply with KDE documentation guidelines
anyways).
So, remove the asciidoc and instead generate man pages from DocBook XML.
I've taken the liberty of using the more specific content tags but the
overall content should be approximately the same.
I probably should have done this a long time ago, but now kdesrc-build
has a man page (mostly to get rid of the 1 Debian lintian hit I saw for
1.13)
I haven't tied it into CMake yet because I'm tired, but it requires
asciidoc and the short story is:
$ asciidoc -d manpage -b docbook kdesrc-build.1.txt
$ xsltproc --nonet /usr/share/asciidoc/docbook-xsl/manpage.xsl
kdesrc-build.1.xml
Of course finding that damn XSL from CMake will be the problem in the
future but I can figure that out tomorrow if no other kind soul does
that for me.
The option can actually still be passed since kdesrc-build accepts
command-line options matching known global option names, but since
we default to removing old log directories there's no reason to add 40
different ways to enable this.
kdesrc-build has supported emailing error messages for some time, at the
conclusion of the build process. There is no easier way to "modularize"
this code than to elide it completely, and given that no one seemed to
use it in the brief poll I conducted, I've removed it.
Script Kiddy
Michael Pyne
Yuri Chornoivan
Burkhard Lück
Valery Yundin
Raphael Kubo da Costa
Pino Toscano