On Thu, Nov 17, 2016 at 11:45 AM, Matthias Kuhn wrote:
> On 11/16/2016 04:02 PM, Aleix Pol wrote:
>> On Mon, Nov 14, 2016 at 12:44 PM, Matthias Kuhn wrote:
>>> Hi,
>>>
>>> I'm a developer of QGIS [1] which makes heavy use of Qt libraries. I was
>>> very
On 11/16/2016 04:02 PM, Aleix Pol wrote:
> On Mon, Nov 14, 2016 at 12:44 PM, Matthias Kuhn wrote:
>> Hi,
>>
>> I'm a developer of QGIS [1] which makes heavy use of Qt libraries. I was
>> very happy to see the work on a KDE flatpak repository which already
>> packages Qt [2].
On Mon, Nov 14, 2016 at 12:44 PM, Matthias Kuhn wrote:
> Hi,
>
> I'm a developer of QGIS [1] which makes heavy use of Qt libraries. I was
> very happy to see the work on a KDE flatpak repository which already
> packages Qt [2].
>
> I have recently been looking into a couple
On Dienstag, 15. November 2016 18:00:34 CET Aleix Pol wrote:
> On Tue, Nov 15, 2016 at 1:16 PM, Matthias Kuhn wrote:
>
> I would like to see how much pyqt increases the size of the (not yet
> optimized) runtime. I agree it can be interesting, but I'm not sure by
> how much.
On Tue, Nov 15, 2016 at 1:16 PM, Matthias Kuhn wrote:
> Hi Aleix,
>
> Thanks for the quick feedback
>
> On 11/15/2016 12:44 AM, Aleix Pol wrote:
>> Hi Matthias,
>> Really happy to see there's interest!
>>
>> On Mon, Nov 14, 2016 at 12:44 PM, Matthias Kuhn
Hi Aleix,
Thanks for the quick feedback
On 11/15/2016 12:44 AM, Aleix Pol wrote:
> Hi Matthias,
> Really happy to see there's interest!
>
> On Mon, Nov 14, 2016 at 12:44 PM, Matthias Kuhn wrote:
>> Hi,
>>
>> I'm a developer of QGIS [1] which makes heavy use of Qt libraries.
Hi Matthias,
Really happy to see there's interest!
On Mon, Nov 14, 2016 at 12:44 PM, Matthias Kuhn wrote:
> Hi,
>
> I'm a developer of QGIS [1] which makes heavy use of Qt libraries. I was
> very happy to see the work on a KDE flatpak repository which already
> packages Qt
Hi Jan,
I agree that not everything should be in there.
That's why I didn't list dependencies like postgres, proj4, geos, gdal
and many more.
The main goal I have here is to minimize the maintenance overhead by
finding the best way to generalize runtimes. E.g. QtLocation is a core
Qt module, so
Hi Jan,
I agree that not everything should be in there.
That's why I didn't list dependencies like postgres, proj4, geos, gdal
and many more.
The main goal I have here is to minimize the maintenance overhead by
finding the best way to generalize runtimes. E.g. QtLocation is a core
Qt module, so
Hi,
if you add your additional dependencies which are not in KDE's flatpak runtime
currently, then I guess it won't have any difference for your users. They will
either have to download a runtime requiring more space or an app bundle/repo
requiring extra space due to QtLocation, QCA and so on.
Hi,
I'm a developer of QGIS [1] which makes heavy use of Qt libraries. I was
very happy to see the work on a KDE flatpak repository which already
packages Qt [2].
I have recently been looking into a couple of different approaches to
ship app bundles and flatpak sounds like a very interesting
11 matches
Mail list logo