Hey
So we already have kpmcore packaged here [1], which might be a better
place to start.
Cheers
Rohan Garg
[1]
https://packaging.neon.kde.org/kde-extras/kpmcore.git/tree/debian?h=Neon/release
--
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-talk
Hi
> And again, Rohan, my apologies.
Apologies accepted. Let's move forward and keep doing awesome work together :)
Cheers
Rohan Garg
--
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-talk
> So yeah, figuring out where qmake is called from PATH and fixing that
> to use Qt5::qmake LOCATION would be best here.
>
Fair enough. I'll poke it a bit more to see why it's resolving qmake
from PATH in certain projects.
Cheers
Rohan Garg
--
http://lists.alioth.debian.org/cgi-bi
and export
QT_SELECT=5 directly in debian-qt-kde.mk instead of each packaging
doing it for themselves.
Since this only affects v3 of the script, KDE4 packages using v2
should be un affected by this change.
Cheers
Rohan Garg
--
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-talk
'm missing here?
Right, I think I forgot to mention before that we're using
KDE_USE_QT_SYS_PATHS in the packaging scripts which makes triggers a
call which essentially looks for qmake, and in some cases, the qmake
symlink points to a non existent Qt4 qmake which causes
dh_auto_configure to fail
2015-04-23 15:28 GMT+02:00 Lisandro Damián Nicanor Pérez perezme...@gmail.com:
Does [0] works without patching qt4?
I've been told it does work, so I guess it's between me forking the
Qt4 packages and maintaining them by myself or using that hack.
Ah well ...
[0]
I'll stand up to ship it :)
Regards,
sandro
I can help with whatever needs fixing and what not.
Cheers
Rohan Garg
--
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-talk
-
Could we move this forward maybe? :D
@Pino would be awesome to have any comments you might have against this :)
Cheers
Rohan Garg
--
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-talk
