| Git Clone URL: | https://aur.archlinux.org/onedrive-abraunegg.git (read-only, click to copy) |
|---|---|
| Package Base: | onedrive-abraunegg |
| Description: | Free OneDrive client written in D - abraunegg's fork. Follows the releases on https://github.com/abraunegg/onedrive/releases |
| Upstream URL: | https://github.com/abraunegg/onedrive |
| Keywords: | onedrive |
| Licenses: | GPL-3.0-or-later |
| Conflicts: | onedrive, onedrive-abraunegg-git, onedrive-bin, onedrive-fork-git, onedrive-git |
| Provides: | onedrive |
| Submitter: | Pete |
| Maintainer: | Matr1x-101 (yogeshm.007) |
| Last Packager: | yogeshm.007 |
| Votes: | 122 |
| Popularity: | 2.72 |
| First Submitted: | 2019-03-29 10:46 (UTC) |
| Last Updated: | 2025-06-09 14:40 (UTC) |
@JP-Undercover I'm happy to make the package aarch64 compatible, but unfortunately I don't have any opportunity to test it.
Could you:
- Test if simply adding the architecture is enough
- If not, make a patch and send it to me
- Help out if later people need support for aarch64?
(If you want to contact me directly, see the email address in my profile)
In the PKGBUILD the architecture aarch64 is not present, however after checking the GDC and the LDC Wiki both seem compatible with this architecture, and using the liblphobos and ldc packages in a Raspberry Pi 4 running Manjaro-ARM (aarch64) i've sucefully installed the package in the system and after a dry run everything seems to be working.
Also in the github page it has specific instructions for this architecture and several others, which means they are officially supported, so I would imagine the PKGBUILD is incomplete?
Also while installing this on Manjaro-ARM and selecting the default packages, it tries to install libgphobos and gdc on the system, while the first conflicts with gcc-libs, so the only way to build this would be to use liblphobos and ldc. This is just a warning as I am aware that the AUR does not provide support for other arch based distros.
Through the test, there is no problem.
I have pushed a new version now with this change. Please test, and let me know if there are any problems.
I think this is good, thank you very much.
Unfortunately I don't have time to go into depth today, but I think I'll solve this by providing the --with-systemdsystemunitdir=DIR and --with-systemduserunitdir=DIR to the configure script. This will install the systems unit files always, without actually requiring systemd. Looking to other packages (such as e.g. nginx), this is the common thing to do.
What do you think? Would that solve your problem?
@Pete If you use extra-x86_64-build to build, because systemd is missing from makedepends=, the built package will not have onedrive.service and onedrive@.service files.
See: https://pastebin.com/1HTHJ1R9
My suggestion is to add systemd to makedepends=, of course, if you want to add it to optdepends= it is also good.
makedepends=('d-compiler' 'systemd')
@dctxmei Thanks for your comment. Could you elaborate your request a bit more? Unfortunately I can't parse anymore information from the link you provided.
I'm not completely knowing the situation of "systemd-free" arch, but wouldn't adding systems as a dependency exclude those users? And, if systemd-free arch is not a thing to take into account, doesn't that mean that systemd is always present at build time?
Please add systemd to makedepends= so that the .service file will appear.
@abraunegg
Understood!
I just directly built from the repo. Worked fine.
I will be waiting!
Much appreciated!
Pinned Comments
Pete commented on 2019-03-29 10:51 (UTC)
This package can be used as a replacement for onedrive-abraunegg-git. It will be updated on every release from https://github.com/abraunegg/onedrive/releases .