-
Notifications
You must be signed in to change notification settings - Fork 277
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Investigate Appimage #1148
Comments
@pierreporte, well, since it will take distributions some time to adopt QtWebKit NG it could make sense to prepare such packages to not let users wait. |
If all you need is standalone binaries + GUI installer, flatpack is insane overkill. I propose to use more lightweight solutions like QtIFW (see CPackIFW), AppImage, or something in this vein |
@annulen I don’t get the “overkillness” of Flatpak by reading the documentation of both Flatpak and AppImage. Could you do a fast little summary of the pro and cons of Flatpak, Snappy, Appimage and QtIFW? Besides this, we also need to consider which packaging system is the most used. It would be a pity that the user would have to install a whole packaging system for one program. |
There is no need to install anything to use Qt IFW. You download installer and execute it. That's all.
It runs application in a chroot with almost complete OS, which is distrributed within the package, while right approach is to pack just Qt and a few other libraries, and use libc, X11 and all other stuff fronm the host system. |
Which you can do with AppImage @annulen |
Can AppImage packages be integrated to the system like any other application? That is, Otter will automatically appear in the right menus and could be set as the default browser? Also, if someone installs Otter with the package manager provided by the distribution and with the AppImage package, what happens? |
An AppImage is just a self-mounting ISO that contains an application and everything it needs to run which cannot be assumed to be part of the base system. Hence, the application inside the AppImage can copy a If someone installs Otter with the package manager provided by the distribution and with the AppImage package, then both are available and can be used. See appimage.org for information; a large number of example AppImages (including some browsers) are available for testing on https://bintray.com/probono/AppImages. |
It’s great then. We could then have classic packages for stable releases and AppImage packages for weekly and beta without any interference. |
Yes, for updating e.g., from weekly to weekly, binary delta updates could be used (so that users only download the bytes that have changed, making updates quick and efficient). |
According to Jesse Smith’s post Opinion on DistroWatch, AppImage clearly seems to be the better packaging system. |
I managed to get a snap working in --devmode, it does not have flash working at the moment. Working on those issues now. |
I was willing to propose a Chocolatery package for Windows, since Firefox and Chrome are already available, and it has very similar features to the package managers on Linux (installation, un-installation, update, dependencies). However, someone already did one but it is clearly outdated. In fact, it is made by @adgellida who clearly states that his Chocolatery packages are unmaintained. Should we consider to ask him to give us control on the package? |
Doesn't Otter have auto update on Windows? |
@mariokamenjak, we have support for auto update, but currently it is used only as update notification. |
In this case it makes sense to provide Qt IFW packages for all platforms |
Well, I am glad that a snap package is in the pipeline though. |
Is there something I could help you with regarding the AppImage? |
@probonopd, I'm going to give it a try for this beta (which means this week, in worst case after beta itself), this way Linux users could make use of revived QtWebKit which is here even bigger update than under Windows. ;-) |
Great ! I recently tried the AppImage file for OpenShot 2.1 (the new stable version after 3 years of work!) and it didn’t work. Can’t wait to test the Otter package. |
While beta got delayed after all I'm still planning to try to create Appimage for one of upcoming weeklies. |
Generated an experimental AppImage based on the trusty ppa, please try: Here is the recipe that was used to produce it: |
@probonopd I tried your AppImage and it doesn’t work. It asks me if I want do create a .desktop file, but right after it quits saying that libwrap.so.0 is missing.
I use an up to date Archlinux where Otter runs usually fine. |
@Frenzie, so, does it actually work for you? ;-) |
Maybe it would be easier to do using debian oldstable, Ubuntu trusty or something along these lines? |
@probonopd, maybe, but that CentOS instance is finally ready to use. ;-) |
You don't need OS instance, you need provisioning script (or puppet manifest, or whatever else you are familiar with) |
BTW, wheezy does not provide gstreamer 1.0. You should really consider building with jhbuild, it requires only very basic system dependencies |
Sorry, I haven't actually tried it yet. Spending time with family. :)
…On Dec 27, 2016 9:11 AM, "Michał" ***@***.***> wrote:
@Frenzie <https://github.com/Frenzie>, so, does it actually work for you?
;-)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1148 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAMYBQYiNuosQ65quGEbO5t1cck8MZzGks5rMMgTgaJpZM4Izi4K>
.
|
@annulen, maybe later, so far I've invested too much time into current solution. ;-) @probonopd, is there some way to force |
Testing in Manjaro full updated in the unstable branch:
As it can be fixed appending |
Posting this from http://otter-browser.org/tmp/otter-browser-0.9.12.dev-x86_64.AppImage on @c-cesar: Do you see any error messages when you launch it in the command line? |
@c-cesar this is a squashfs-based type 2 AppImage. To mount:
|
@probonopd I just tested your AppImage. It refused to start because of missing “language dictionaries”:
I am running an up-to-date Archlinux. |
@probonopd, is there any generator for launch scripts? @pierreporte, it seems that for some reason system QtWebKit got picked up. I've managed to create version with bundled GStreamer, not that video playback might be choppy (I've heard that another branch contains updated player): |
@Emdek, |
@probonopd, I'm more interested in that dialog shown by your experimental AppImage linked earlier, is this that one? |
Well, I use the desktopintegration script for my non-linuxdeployqt-generated AppImages, but I think you could make it work with the linuxdeployqt-generated AppDir as well. To see how I use it, it's best to download a simple AppImage and look at
Instead of the compiled As for linuxdeployqt, it uses patchelf to make it load libraries from inside the AppImage rather than from the base system, if available. Turns out this is still a bit buggy (PRs welcome!). |
@probonopd there is no launch script, but there is a Exec field in otter-browser.desktop where i can put the flag. I wanted to append it because the error message listed the platform plugin. But the cause is the ambiguity of the message. It could not find or load. So, I run the ldd in xcbplugin and find my problem: libselinux.so.1 => not found. SELinux is not in Arch or Manjaro repos, but is installable. After I installed libselinux I can start Otter.
|
Agree, would be best to compile without SELinux. |
@probonopd, thanks for the tip, I'll experiment with that script later. Custom Qt build might be a problem... @c-cesar, try that newer build, it includes GStreamer 1.10 so it gets more points for multimedia support. |
Here is another attempt, linked against GStreamer 1.10 but without bundling it (bundled can lead to no audio, most likely thanks to Pulse Audio) and including both |
The new AppImage runs, but started a blank profile, instead of using my usual, like the otehrs. |
@c-cesar, fresh profile? That is weird. That test is borked, it assumes that MSE is available, to get results you need to enable it in about:config (QtWebKitBackend/EnableMediaSource) but I suggest to disable it after running test, since it might cause issues with video playback on YT. |
I launched it from a terminal session logged with another user. my bad. |
@Emdek just out of curiosity, why not on https://github.com/OtterBrowser/otter-browser/releases? |
@probonopd, while sf.net has own set of issues it is still superior to github when it comes to distributing binaries (SFTP access, statistics etc.). |
For a really long time, installation of software under Linux was possible by using distribution-specific package manager or by compiling the whole programme. The package managers work really well but if the desired programme is not present or is too old, the compilation was the only way and it may be really long and not easy for someone not really into computers. For several months now, two thing came out to simplify the installation of software under Linux: Flatpak (formerly known as XDG-Apps) for all distributions and Snap for Ubuntu only. Flatpak and Snap packages are distributed like Windows installers and provide sandboxed applications. For now, according to the Flatpak website, it is available in Archlinux, Debian, Fedora, Mageia and Ubuntu.
I think it would be good to provide Flatpak packages for Otter. Flatpak being available to Ubuntu, Snap could be avoided. Users could install each weekly or beta version without having to compile or wait that the package maintainers do it. With Flatpak only, virtually all distributions providing Flatpak can be targeted and it could even be official packages.
The process of building a Flatpak package seems quite easy and fast so the additional work should be minimal after the first time.
Personally, even if I compile Otter directly from the git repository (from the AUR package in Archlinux), I will use the Flatpak package if it is made available.
The text was updated successfully, but these errors were encountered: