This allows for many useful language improvements, especially support
for new package declaration syntax and the use of array/hash operators
on references. 5.14 has been out for a few years now, and AFAIK is now
available in all recent distros.
Albert Astals Cid fixed dependency-data, Ben Cooksley fixed the module
layout of kde/kde-baseapps* in kde-projects, now to fix the recommended
build order in the samples provided.
The relevant KDE bug for the module moves is Bug 316629.
A prompt is used to ask if a proxy is required, unless the normal
http_proxy env. variable is set, at which point the proxy URL will be
queried for directly (and the value of http_proxy used as the default).
This should implement wish 305410.
BUG:305410
FIXED-IN:1.16
It was difficult to see the error message until I thought to remove the
'clearScreen' call before throwing the "dialog canceled" exception, but
the cause of bug 300911 (Setup quits unexpectedly when choosing a custom
install directory) is due to the dialog(1) command failing when it
couldn't create a window big enough for the directory selector.
Apparently the "height" parameter does not include all the curses
window decoration.
(Fixed-in flag reflects the kdesrc-build version)
BUG:300911
FIXED-IN:1.16
I use 'framework' kind of liberally in the script to mean base/essential
libraries for KDE development, but it has understandably been confused
with the frameworks branch of kdelibs. Rename.
This is also fixed now in the KDE build metadata but might as well have
it right here too.
Thanks to Jan Hackel for the report and diagnosis.
BUG:298401
Aurélien Gâteau has informed me that libdbusmenu-qt has shifted
development awhile ago to be hosted on Canonical's Launchpad, which uses
the bzr SCM. He also informed me that the gitorious.org repository which
kdesrc-build had been recommending is no longer maintained, and very
politely requested help with having kdesrc-build support bzr.
On the one hand I really don't think it's necessary at this point to
allow for building bleeding-edge libdbusmenu-qt (I would be surprised if
kdelibs depended on a libdbusmenu-qt that hasn't been packaged for
months).
But on the other hand if it does become necessary we will be ready, and
this fits in well with the idea of building Qt and all of the
"kdesupport"-style libs in between Qt and kdelibs.
Unfortunately this shows I still have further to go in my
refactoring/documentation efforts since I still had to end up
implementing the support. But, it was certainly a much easier job than
it would have been before I had started fixing the codebase. This patch
was coded over no more than probably an hour or so (if that time were
consecutive... ;) and Aurélien tested overnight and after fixing my one
mistake reported that it worked swimmingly.
After installing bzr today I can report this works for myself as well,
and without having to insert "hacks" throughout the code to make it
work.
CCMAIL:aurelien.gateau@canonical.com
Pretty much what it says in the subject, although it depends at this
point on auto-detecting the proper build system correctly.
If you want to see what build system kdesrc-build thinks is required,
run with --verbose or --debug, and the build system will be displayed
with the module name during the build phase.
I mistakenly said an earlier commit implemented this feature though,
it's actually *this* commit.
CCBUG:265255
There is already a framework-phonon module-set with the right entry for
phonon (phonon/phonon instead of phonon, which will build all
phonon-related modules).
kde-baseapps must precede kate and konsole since kate/konsole are
logically under kde-baseapps. Thanks to dfaure for finally nailing down
the cause of this bug.
I will keep the bug open until I develop a way to detect and
automatically correct the module ordering should this happen again.
CCBUG:283127
If a user generates a configuration file that kdesrc-build won't pick up
by default, then show a message after the setup script runs warning them
about that and letting them know what they have to do.
Now it supports:
* Backup existing configuration and overwrite
* Custom configuration filename.
* It even automatically falls back to a tempfile if backup fails.