| sootstone | |
| Apr 30 2020, 10:45 AM |
| F5930600: image.png | |
| May 13 2020, 4:13 AM |
ProtonMail Bridge for Linux is now out of Beta and is also now open source.
| R5138 protonmail-bridge | |||
| D10348 | R5138:f2810d070e69 Inclusion of protonmail-bridge resolves T8937 | ||
To whoever reviews this package request. While the project has no tagged releases currently on github, it has been requested and future releases will be tagged.
Hi. All new releases from now on are going to be tagged here on GitHub as well.
Source: https://github.com/ProtonMail/proton-bridge/issues/10#issuecomment-617567920
EDIT:
I should also point out that usage of protonmail-bridge is for paid protonmail accounts only.
The ProtonMail Bridge is an application for paid users
Source: https://protonmail.com/bridge/
Boooo
Hi! There is a version out, it is 1.2.6!
I would like to like to volunteer as a maintainer of that package.
This is my first eopkg that I will build!
@JeffLabonte As discussed above. Their code repository did not originally tag releases. But they've agreed to start doing so for future releases.
It's open source and will need to be compiled from source, not repackaged from a pre-compiled binary (Such as what is shown in the screenshot) you can find the code on the their github project page.
https://github.com/ProtonMail/proton-bridge/releases
Latest appears to be 1.2.7-Beta so they have started tagging releases but you'll still have to wait until a stable tagged release on github is available, as Solus only accepts stable software, no alpha, beta or release candidates (There are few exceptions).
Of course nothing is stopping you from starting to learn packaging now using the beta version. :)
What would be the process to become maintainer of this package? Is there any good examples on how to package this project?
By the way, there has been a few release since the last time I commented this ticket.
Thanks guys!
As it has been accepted for inclusion and flagged as needing a maintainer, you just need to do the work figuring out how to package protonmail-bridge, test it and submit it for review https://getsol.us/articles/packaging/
There are no universal examples for packaging, that is not possible. There will be differences between different software and how one distribution packages that same software compared to another. While it is possible to learn how to do certain things from viewing other peoples work, it can only go so far, it will still require a base understanding of what you're doing.
If you get stuck and have some specific questions. You can jump on IRC in the #Solus-Dev channel (joining this channel requires a registered account on freenode).
I worked on packaging protonmail-bridge... It is mostly done, but I have noticed that protonmail-bridge ask for me to update the software even though I am using the latest version available.
I have opened an issue on GitHub, so I hope I will have some news about this issue.
I still need to add the description, the .desktop file, and change the license!
What is the output of proton-bridge --version
My guess is your building it from the tarball which is usually what you should do. But some software, like micro does not identify its version properly if not built from a git clone an causes issues.
I was going to maintain this myself before I realised it was a paid only feature and abandoned it, so I just re-packaged it an I don't get the update message.
My output is
INFO[0000] Run app appLong="Protonmail Bridge" appShort=bridge args="[proton-bridge --version]" build="2020-10-09T03:40:12+0000" pkg=main revision=01a8c9e9d7 runtime=linux version=v1.3.3-git Protonmail Bridge version v1.3.3-git (01a8c9e9d7) 2020-10-09T03:40:12+0000
I found out that the archive doesn't work at all... Only the git repository using the tag v1.3.3 works!
