search

Nextbird / nextbird

“Life support” fork of Corebird, a native GTK+ Twitter client
GNU General Public License v3.0
11 stars 1 forks source link

Distribution mechanisms #9

Open lucaswerkmeister opened 5 years ago

lucaswerkmeister commented 5 years ago

How can we get this app to the people?

(To be clear, wherever the above says “I”, someone else is also free to take over :) )

Thoughts? Other suggestions?

Alexmitter commented 5 years ago

Why not do a ppa for apt based distros? Should be a easy way to distribute for those without being depended on the old maintainer.

x80486 commented 5 years ago

I would put all the effort on the Flatpak, since it's cross-distro...and pretty much what everyone is targeting these days (along with Snaps). All the other packages just create more noise. Of course, if someone is used to PPAs and things like that, they would have a strong opinion on this.

lucaswerkmeister commented 5 years ago

A PPA is another option that I hadn’t thought of, thanks. (But aren’t they Ubuntu-specific?) I have no experience in setting them up, though – do you know how to do it? (I couldn’t even figure out how one would go about updating the existing package – apparently, the git repository of the source package contains the Debian build files and the rest of the source code in one tree, and I don’t know how one is supposed to update the source code part.)

Alexmitter commented 5 years ago

@x80486 i have a strong opinion against Flatpak simply because i don't want to install their whole framework. And i am not the only one disliking this concept. And no, not everyone is targeting it today, if so, i would be in big fear for the Linux Desktop

@lucaswerkmeister No, PPAs are basically those sources of lists all APT based distros use. More or less. You may add them different on other APT distros but the mechanism should be the same. I guess this should apply to all apt distros if they don't already have this tool: http://www.webupd8.org/2014/10/how-to-add-launchpad-ppas-in-debian-via.html

Alexmitter commented 5 years ago

@lucaswerkmeister Personally i have no experience setting up a PPA, but i guess as always it should not be bad documented. It is just my idea since i consider it straight forward and simple to use, simpler then trying to get help from the old project maintainer that seems to have zero interest.

TingPing commented 5 years ago

May I just strongly suggest not silently changing packages to a new upstream. You should rebrand to avoid user confusion. Corebird is dead and this is a new fork; A new project.

Alexmitter commented 5 years ago

@TingPing There is already a open thread about a name change in #5 . But it seems @lucaswerkmeister does not see a need to change so far.

TingPing commented 5 years ago

Well "need" is a bad term. Legally I doubt Timm ever trademarked it nor would he seek legal action. So no of course it isn't needed.

This is just a personal choice to not silently continue under the original projects brand which feels dishonest to users (who may think the original developer is still working on it) and perhaps dis-respectful.

freecicero commented 5 years ago

I second the comment above against flatpack. Not that i would encourage this alternative, but I have used some Appimages with success, and I gather that those do not have the same tie-in issues as flatpack or snap.

But whatever you decide I will try to make work - I just appreciate your working on this.

pizzadude commented 5 years ago

I don't have anything against flatpak, snaps, or PPAs. I use all 3. (Although snaps have problems with themes) Looking forward to being able to install this easily with either of those methods. I would probably go with flatpak though, because of sandboxing, and also that's how I have Corebird installed right now (even though it's discontinued)

lucaswerkmeister commented 5 years ago

I’ve built Ubuntu (Bionic, Cosmic) and Arch packages now and attached them to the 1.7.4.2 release. (The process to build them is described in the wiki.) Flatpak users can also build from flathub/flathub#716, using the command in https://github.com/flathub/flathub/pull/716#discussion_r232488586.

lucaswerkmeister commented 5 years ago

A package for Debian Stretch is now also attached to the 1.7.4.2 release, though I’m unable to test it. Let me know if it works!

freecicero commented 5 years ago

Yes that build works great for me on MX17 in Stretch -- thank you!!!!!

zelmor commented 5 years ago

I have reported to the Debian project that the developer has abandoned the project, as well as the limited functionality of the software since the API breaking.

The last patch in sid was in March 2018, so with Buster coming out 2019, it would be over a year old, with limited functionality. If this community effort picks up and you either remake the software or achieve full functionality patching the existing codebase, please contact me over github and I can act as a Debian facing maintainer.

In the meantime please consider setting up a ppa so that we do not litter the Debian archives with software of limited functionality. Those who care for this software can get it from source or via .deb/ppa.

Alexmitter commented 5 years ago

@zelmor there is now a .deb under the releases tab.

lucaswerkmeister commented 5 years ago

@zelmor ack, but note that we’ll almost certainly rename the software (see #5 – it’s basically just waiting for me to get around to it, might happen tomorrow)

probonopd commented 5 years ago

Let me know if you are interested in making an AppImage. http://docs.appimage.org/

freecicero commented 5 years ago

Probonopd I hope that there will be enough interest for an Appimage, because that is what I want. I have several computers running Jessie in addition to Stretch and I have had good look with Appimages every time I have tried them. I am not smart enough to help develop but I would be glad to test.

probonopd commented 5 years ago

Actually I remember the lead developer being dismissive of the idea: https://github.com/baedert/corebird/issues/518

rodneyrod commented 5 years ago

As far as Arch goes, someone has made an AUR with their own patches to Corebird here: https://aur.archlinux.org/packages/corebird-non-streaming-git/ https://github.com/IBBoard/corebird/tree/non-streaming

Maybe it'd be easier to get in touch and consolidate efforts?

lucaswerkmeister commented 5 years ago

@probonopd no opinion on AppImage so far. If it helps users get the app, it could probably be useful – if someone else will do the work of packaging it up, even better :)

@rodneyrod oh, that’s great, thanks for the pointer. I’ll take a closer look at the individual commits later, but let’s ping @IBBoard as well.

IBBoard commented 5 years ago

That AUR package isn't me, but the GitHub repo with patches (and working DMs and lists and "streaming") is obviously mine. I build RPMs for openSUSE on the Open Build Service - https://build.opensuse.org/package/show/home:IBBoard:desktop/corebird.

Personally, I have no plans for using Snapper/Flatpack/anything else for any apps. To me, the whole point of Linux packages is to not bundle dependencies so that they can be properly secured and maintained!

rodneyrod commented 5 years ago

I think the best course of action would be to pool everyone's changes into a new hard fork project to increase visibility and retire any packages that are tied to a particular implementation, such as the existing AUR, or have it directed to the new project.