---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/109492/
---
(Updated March 31, 2013, 10:19 p.m.)
Status
--
This change has been m
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/109492/#review30191
---
This review has been submitted with commit
81fd37ec62cf8f06499
On sábado, 30 de março de 2013 20.33.09, Elvis Stansvik wrote:
> Does KDE need the Qt tools to be in PATH for some reason? I tried
> commenting those lines and it started fine without them.
Yes, it needs the qdbus executable.
--
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/109792/#review30173
---
To be honest I don't like adding yet another configuration opti
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/109404/#review30172
---
Is this not needed anymore to work under Arch environment?
-
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/109792/
---
(Updated March 31, 2013, 4:07 p.m.)
Review request for kde-workspace and S
Hi all,
Line 19-33 of the startkde script reads:
# in case we have been started with full pathname spec without being in PATH
bindir=`echo "$0" | sed -n 's,^\(/.*\)/[^/][^/]*$,\1,p'`
if [ -n "$bindir" ]; then
qbindir=`$bindir/kde4-config --qt-binaries`
if [ -n "$qbindir" ]; then
case $PAT
