|Subject:||Re: [Ring] About a flatpak package|
|Date:||Mon, 3 Jul 2017 18:49:19 -0400|
I have been trying get the flatpak of ring, but I am failing to compile dbus-c++ inside flatpak... as it is not a part of any of the available runtimes--On 1 February 2017 at 07:15, Aditya Shah <address@hidden> wrote:I will try packaging ring, though no promises as this is my first app. Also as far as problems is concerned, we don't really need to package ring for every distribution, just packaging a flatpak should work on all distributions, this will reduce distribution delays. Containerization is obviously a plus.On Jan 31, 2017 11:32 PM, "Guillaume Roguez" <guillaume.roguez@savoirfairel
inux.com> wrote:From the website - flatpack.org - they write that flatpak'ed applications can run in a sandbox.
That's the major improvement for Ring itself.
@Aditya: I hope that the Stepan's list help you to go ahead. let us know your progress. thanks.
----- Le 31 Jan 17, à 17:15, Stepan Salenikovich stepan.salenikovich@savoirfair
elinux.coma écrit :
> ----- On Jan 31, 2017, at 3:52 PM, Aditya Shah address@hidden wrote:
>> I was thinking it is possible to create and distribute a flatpak of ring. I
>> don't know what all dependencies are present for ring as whole, but
>> shipping a flatpak should be able to solve a lot of problems.
>> *Aditya Shah*
> I think it would be cool to get it to build in flatpak, but what exactly
> are the problems that you want to solve using flatpak? I guess it could
> be slightly easier than building from source... though I haven't actually
> tried using flatpak myself.
> Here's a list of build dependencies taken from the Debian control file
> we use to package Ring:
> Build-Depends: debhelper (>= 9),
> # gnome client
> libwebkit2gtk-4.0-dev | libwebkit2gtk-3.0-dev,
> # ring-daemon
> # other
|[Prev in Thread]||Current Thread||[Next in Thread]|