Sorry for pulling this old thread, and also sorry for keeping this issue pending for so long. I have manager to compile the entire ring under flatpak <https://flatpak.org>. the completed manifest with required patches are on github <https://github.com/adityashah1212/cx.ring.Client-flatpak.git>. Please have a look. Also I am not able to launch the application, it seems I am missing some dbus names used. I am not sure which and how to fix them, please look at it, a PR would be much appreciated. After it successfully runs I intend to publish it on flathub <https:/fathub.org>, through a PR on github <https://github.com/flathub/flathub>.
Regards, Aditya Shah On 9 February 2017 at 20:24, Aditya Shah <[email protected]> wrote: > 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 <[email protected]> > 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" < >> [email protected]> 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. >> >> // Guillaume >> >> ----- Le 31 Jan 17, à 17:15, Stepan Salenikovich >> [email protected] a écrit : >> >> > ----- On Jan 31, 2017, at 3:52 PM, Aditya Shah >> [email protected] wrote: >> > >> >> Hi, >> >> >> >> 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. >> >> >> >> -- >> >> *Sender* >> >> *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), >> > autoconf, >> > automake, >> > cmake, >> > libtool, >> > autotools-dev, >> > # gnome client >> > libebook1.2-dev, >> > libclutter-gtk-1.0-dev, >> > libclutter-1.0-dev, >> > libglib2.0-dev, >> > libgtk-3-dev, >> > libnotify-dev, >> > qtbase5-dev, >> > qttools5-dev, >> > qttools5-dev-tools, >> > gettext, >> > libqrencode-dev, >> > libappindicator3-dev, >> > libnm-glib-dev, >> > libwebkit2gtk-4.0-dev | libwebkit2gtk-3.0-dev, >> > # ring-daemon >> > libdbus-1-dev, >> > libdbus-c++-dev, >> > libupnp-dev, >> > libgnutls28-dev, >> > libpulse-dev, >> > libasound2-dev, >> > libexpat1-dev, >> > libpcre3-dev, >> > libyaml-cpp-dev, >> > libboost-dev, >> > libsndfile1-dev, >> > libxext-dev, >> > libxfixes-dev, >> > libspeex-dev, >> > libspeexdsp-dev, >> > uuid-dev, >> > libavcodec-dev, >> > libavutil-dev, >> > libavformat-dev, >> > libswscale-dev, >> > libavdevice-dev, >> > libopus-dev, >> > libudev-dev, >> > libgsm1-dev, >> > libjsoncpp-dev, >> > libnatpmp-dev, >> > libva-dev, >> > libcrypto++-dev, >> > # other >> > yasm, >> > libsamplerate0-dev >> > >> > -stepan >> >> >> > > > -- > *Sender* > *Aditya Shah* > -- *Sender* *Aditya Shah*
