Arch Linux User Repository

I see, I understand it. But please wait for the next release of Whalebird. I will change it until the next version.

Thanks for the move to a source build. Please have a look at how whalebird-desktop was doing this though because there is one more major step to go here. You're currently building from source but you end up installing a complete extra (vendored) copy of Electron. The Arch Electron package guidelines call for this to be eliminated and depend on (and use) the system copy of Electron instead.

OK, I rewrite this to build from source code.

Addendum: I'll put off the merger a few days if you'd like you can repost this as -bin, then file a merge request for this package into the new name to retain the comments / votes.

Also note that this package should not provide whalebird (it is whalebird) but the -bin variant when you set that up should provide & conflict whalebird.

What @lmartinez-mirror says here is correct, this package is miss-named. What is posted at whalebird-desktop should be posted here (hence I'm going to approve the merge request of that package into this one. However they are not the same thing at all and what is currently posted here should be reposted as a whalebird-bin package, then the content of this one replaced with the source build. This is more than a suggestion, the AUR guidelines require that packages be named -bin if there is the possibility of a source package (personally I would like to see that for all bin packages, but the current guidelines only require it for source-available projects).

Hi, this package should build from source since it doesn't have a "-bin" suffix.

(full disclosure, i maintain whalebird-desktop, which builds from source and uses the system electron instead of pulling its own)

@homk Hi, I'm a developer of Whalebird. This package is official package of Whalebird, so this package always follows the latest release of Whalebird.

I don't know about whalebird-desktop.

Hi. What is the difference between this package and whalebird-desktop ?

@matthias.lisin, thank you for the good explanation! Yeah, I understand the problem with future electron updates...

@spsf64 That's a decision I struggle with for every Electron package I maintain. I went with electron 7 because it is used upstream and is available in the official repositories.

There is no big reason to use electron7. However, when Electron 9 arrives and the electron package is updated in the Arch repos, it might break the application without prior notice and I have to act fast to revert the dependency to electron7 or then electron8.

But since there are not many users right now, I can totally update it to electron.