-
Notifications
You must be signed in to change notification settings - Fork 140
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
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
port to freebsd #125
Comments
I can't think of any features that won't work on BSD. Even DBus-notifications should work. We just need someone with a FreeBSD desktop to test it. :-) |
Note: other *BSD are of course also welcome. I just mentioned FreeBSD because I know pyinstaller supports it and borg also offers fat binaries for FreeBSD. Besides that part, other BSDs should work as well. |
Closing this, as it's included in #126 . |
Well, it is a requirement for #126, but first getting it running and tested and then packaging it as a fat binary are still different things. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Maybe usage of a stalebot should be reconsidered. I often find it annoying if a brainless bot closes stuff (or tags as stale and then closes soon later) that is not done / not fixed, just because there was no activity for some time. |
We do get a lot of support requests and questions recently. I'd like to close those after some time. Any issue that has a useful label is already excluded. For those one I wasn't sure, but let's add "task" for now. |
See here for the labels we keep open forever: https://github.com/borgbase/vorta/blob/master/.github/stale.yml#L6 |
That helps a bit, but only if a maintainer has time to put such a label. If not, the dumb bot might still close valid issues. |
We usually label every issue properly when it comes in or when new information emerges. So I don't worry much about that part. Worth a try. |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
freebsd is a quite popular platform and i guess vorta could be easily run there.
i don't use freebsd myself, so i won't do the porting / testing, but wanted to put some notes here for whoever wants to help with it:
as vorta runs on linux and macOS already, i do not expect major complications with the port, should mostly just work "as is".
a fat binary made with PyInstaller could be offered for freebsd also - PyInstaller supports freebsd and the vorta.spec file should just work. when binaries are built on a specific freebsd version, it is likely that they run on any as old or newer freebsd version, so building on a relatively old (but still supported) version might be preferable.
there is a borg fat binary for freebsd64, it needs to be put into
bin/
(asbin/borg
) before building the vorta fat binary (if you want it included and not requireborg
to be already available on the target system)The text was updated successfully, but these errors were encountered: