I have the mapping applications distributed via Flathub and the experience
has been very good so far. In some aspects its similar to what we have now
- you rely on the runtime (Platform in flatpak lingo) and have to bundle
all extra libs with it. Libs are described using via build scripts and
Hello, everyone!
Talking about flatpak: there's even a bit aggressive criticism about it --
http://flatkill.org/
I am personally not against this technology completely, but probably more
into making more of an effort to provide better system side libraries.
пн, 11 февр. 2019 г. в 00:16, Martin
Sun, 10 Feb 2019 23:05:28 +0200 E.s. Rosenberg
:
Flatpak would make our phones so much more insecure - instead of Jolla
updating bad/insecure libraries (which also happens at a pace that
leaves to be desired) you become dependent on the devs of the
application you are using doing that.
I
Flatpak would make our phones so much more insecure - instead of Jolla
updating bad/insecure libraries (which also happens at a pace that leaves
to be desired) you become dependent on the devs of the application you are
using doing that.
Since Jolla tries to have one of its' claims to fame be
Sun, 10 Feb 2019 09:56:06 +0200 Rinigus :
Morning,
suggestion to consider Qt 5.12 in /opt comes from the following:
* newer web engine
* we can use and contribute to the code written for Plasma with its
Kirigami
It will not bring native new applications, we don't have Silica for
it.
Sun, 10 Feb 2019 12:20:31 +0100 Lukáš Karas :
Hi all
To sum up, no idea how much we can help with 5.9 transition and what's
holding it back specifically.
From the Fosdem discussion, I feel like there is no big technical issue.
There was message that majority of SFOS core components already
Oh, for some reason the project was indeed rebuilt by 07-Feb-2019.
Last time I tried it two month ago and it worked well :-(.
I fixed some small new issues and now, wow, the problem with wayland is gone!
This opens the possibility to develop and deploy at least the limited
QQC2-based applications
> Dmitriy: I don't know whether you can mix different Qt versions in the
same application.
> In this respect, yes, you could probably ship Qt 512 stack fully, but
would probably have
> to stay away from the system-provided Qt.
Sorry, my wording was a bit misleading.
What I actually meant was: If
No go, file conflicts appeared for several packages trying to overwrite
qt56 installation. For example, qt5.9-qtdeclarative-qtquick was trying to
write /usr/lib/libQt5Quick.so.5 . I presume something changed in OBS and
your prefix path wasn't picked up.
Rinigus
On Sun, Feb 10, 2019 at 1:01 PM
Hi all
>
> To sum up, no idea how much we can help with 5.9 transition and what's
> holding it back specifically.
>
>From the Fosdem discussion, I feel like there is no big technical issue.
There was message that majority of SFOS core components already has branches
prepared for Qt 5.9.
The keypoints of the build:
- upstream Qt-5.9.6
- Q_OS_SAILFISH platform [1]
- Sailfish Theme added as a plugin instead of direct
QGenericUnixTheme patching [2]
- _qt5_version re-defined in the OBS project config [3] (default value
defined in qt5 macros).
- qt5 macros [4] extended and
Nice work,
so, there is already something similar done. Can't find where do you define
_qt_prefix for your SPEC (
https://git.merproject.org/Kaffeine/qtbase/blob/sailfish-platform-5.9/rpm/qtbase.spec).
There are also bunch of conflicts defined there, no idea whether they
interfere.
Which issues
How about focussing on the 5.9 -> 5.12 transition instead?
if you start from the work of jolla, you will speed up the process.
tortoisedoc
On Sun, Feb 10, 2019 at 11:17 AM Alexander Akulich <
akulichalexan...@gmail.com> wrote:
> Hi,
>
> I experimented with a build in prefix in March 2018. I
Hi,
I experimented with a build in prefix in March 2018. I changed MER Qt
build configuration to make it trivial to install an arbitrary number
of versions simultaneously. I'll make PRs on git.merproject.org once
Qt-5.9 support will be merged to master.
There are two issues — wayland and virtual
Hi,
But even if we get 5.9 it will be ages old and getting fixes for “important
bugs only”...
https://blog.qt.io/blog/2018/02/22/qt-roadmap-2018/
Telling the truth I'm not being familiar with all the details and there must be
reason not to leapfrog to the latest Qt version in Sailfish but
15 matches
Mail list logo
