On March 31, 2013, 6:11 p.m., Àlex Fiestas wrote:
Is this not needed anymore to work under Arch environment?
Yes, this is not needed anymore because qmake always refers to Qt5 in Arch. The
qt4 package doesn't ship qmake anymore and /usr/lib/qt4/bin isn't in $PATH. The
/usr/bin/*-qt4
On terça-feira, 2 de abril de 2013 06.28.49, Andrea Scarpino wrote:
Yes, this is not needed anymore because qmake always refers to Qt5 in Arch.
The qt4 package doesn't ship qmake anymore and /usr/lib/qt4/bin isn't in
$PATH. The /usr/bin/*-qt4 symlinks point to files in /usr/lib/qt4/bin.
And
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/109404/
---
(Updated March 29, 2013, 12:09 a.m.)
Status
--
This change has been
On March 11, 2013, 6:19 a.m., Andrea Scarpino wrote:
I was quite clear: qmake must point by default to Qt 4 if Qt 4 present.
While qtchooser sounds like a great solution to handle this, it only adds
more confusion from a packager view: we cannot have N differents
configurations for qt
On March 11, 2013, 5:19 a.m., Andrea Scarpino wrote:
I was quite clear: qmake must point by default to Qt 4 if Qt 4 present.
While qtchooser sounds like a great solution to handle this, it only adds
more confusion from a packager view: we cannot have N differents
configurations for qt
On March 11, 2013, 5:19 a.m., Andrea Scarpino wrote:
I was quite clear: qmake must point by default to Qt 4 if Qt 4 present.
While qtchooser sounds like a great solution to handle this, it only adds
more confusion from a packager view: we cannot have N differents
configurations for qt
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/109404/#review28931
---
I was quite clear: qmake must point by default to Qt 4 if Qt 4
On March 11, 2013, 6:19 a.m., Andrea Scarpino wrote:
I was quite clear: qmake must point by default to Qt 4 if Qt 4 present.
While qtchooser sounds like a great solution to handle this, it only adds
more confusion from a packager view: we cannot have N differents
configurations for qt
On March 11, 2013, 5:19 a.m., Andrea Scarpino wrote:
I was quite clear: qmake must point by default to Qt 4 if Qt 4 present.
While qtchooser sounds like a great solution to handle this, it only adds
more confusion from a packager view: we cannot have N differents
configurations for qt
On March 11, 2013, 6:19 a.m., Andrea Scarpino wrote:
I was quite clear: qmake must point by default to Qt 4 if Qt 4 present.
While qtchooser sounds like a great solution to handle this, it only adds
more confusion from a packager view: we cannot have N differents
configurations for qt
On March 11, 2013, 5:19 a.m., Andrea Scarpino wrote:
I was quite clear: qmake must point by default to Qt 4 if Qt 4 present.
While qtchooser sounds like a great solution to handle this, it only adds
more confusion from a packager view: we cannot have N differents
configurations for qt
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/109404/#review28925
---
ArchLinux's setup is completely unsupported. I was quite
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/109404/
---
(Updated March 11, 2013, 2:16 a.m.)
Review request for Build System,
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/109404/
---
(Updated March 11, 2013, 2:29 a.m.)
Review request for Build System,
14 matches
Mail list logo
