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
rambox: migrate to use AppImage #109020
rambox: migrate to use AppImage #109020
Conversation
pkgs/applications/networking/instant-messengers/rambox/default.nix
Outdated
Show resolved
Hide resolved
pkgs/applications/networking/instant-messengers/rambox/rambox.nix
Outdated
Show resolved
Hide resolved
This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch) Result of 2 packages built:
|
This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch) Result of 1 package built:
|
@SuperSandro2000 Can you merge this? |
I am not sure if the methodically here is the right one. Also except @Ma27 I couldn't find any of the maintainers. |
This gets a huge thumbs up from me (maintainer of the pro variant of rambox.) 👍 I think ultimately this makes maintaining the package vastly simpler and less problematic. The pro variant of the package has been broken for several weeks now so it needs to be fixed anyway. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm 100% in favour of this change - has my vote! 👍
I don't have a strong opinion on this, but has anybody checked whether the new package will preserve the settings from my original |
@Ma27 Just tested, seems to work fine (tested with |
The same applies to rambox-pro - no settings loss at all. |
Opening URLs seems to be broken after migration to AppImage. Also font and cursor config seem to be ignored. |
@andresilva Can you reproduce this issue with other AppImage programs? If yes, I think it would be better to try to investigate that issue in Maybe opening an issue? |
Yeah the issue seems to be related to AppImage packaging and not specific to Rambox. Will have a look. |
#110636 I have no clue who to ping though. If someone knows who's responsible for maintaining the AppImage packaging support please cc them on that issue. |
Motivation for this change
The motivation comes from PR #108787: AppImage is the official and using it should avoid some issues.
Also, migrating both packages (instead of only rambox-pro like #108787) can make maintaining both packages easier. There is now a
mkRambox
function that abstract most of the build process.Things done
sandbox
innix.conf
on non-NixOS linux)nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
./result/bin/
)nix path-info -S
before and after)