Package Details: onedrive-client-git r270.be86e8b-1

Git Clone URL: https://aur.archlinux.org/onedrive-client-git.git (read-only)
Package Base: onedrive-client-git
Description: A Microsoft OneDrive and OneDrive for Business client for Linux, written in Python3.
Upstream URL: https://github.com/derrix060/onedriveClient
Keywords: onedrive
Licenses: MIT
Replaces: onedriveclient-git
Submitter: Modelmat
Maintainer: Modelmat
Last Packager: Modelmat
Votes: 2
Popularity: 0.003743
First Submitted: 2019-01-07 01:00
Last Updated: 2019-01-07 01:24

Pinned Comments

Modelmat commented on 2019-01-07 01:32

Tests appear to check the dependency versions, so there is no check() PKGBUILd function. If you wish to run tests, run python setup.py test in the download git repository.

Latest Comments

Gameborn commented on 2019-10-16 08:08

In the systemd unit, multi-user.target should be replaced with default.target. Otherwise the user unit does not autostart even when enabled.

Modelmat commented on 2019-01-07 01:32

Tests appear to check the dependency versions, so there is no check() PKGBUILd function. If you wish to run tests, run python setup.py test in the download git repository.

Aanok commented on 2018-12-12 16:28

Do you mean about the AUR itself? I think the forums are where you'd want to look.

Thanks for your availability anyways :)

Modelmat commented on 2018-12-12 10:14

Okay then, will do that. I'll just have to get issues fixed on the repository by using the latest version of said packages.

(ps, do you know how to report issues with the aur?)

Aanok commented on 2018-12-11 14:55

Oops, sorry for the late reply.

Personally, I would prefer if the package was better integrated in the rest of the Arch repositories, so I'd avoid a virtualenv. Managing venvs seems like something one would want to do by hand anyways.

Builtin tests can be run by adding the following to the PKGBUILD:

check() {
  cd "$srcdir/$_pkgname"
  python setup.py test
}

You're also right about the package version. It's just a matter of adding the following, then:

pkgver() {
  cd "$srcdir/$_pkgname"
  printf "r%s.%s" "$(git rev-list --count HEAD)" "$(git rev-parse --short HEAD)"
}

Modelmat commented on 2018-12-01 01:09

Yes, just I used to have it this way. I would think that the packages would eventually break compatibility with newer versions.

I have had it in my todo to update it to follow some package guidelines.

I was thinking either someone has the binaries run a virtual environment so that we can manage with pip, or figure out how to run tests (which would fail when packages become incompatible). Please tell me what you would prefer.

(sidenote, this package is also several major commits behind in terms of actually commits and I sussing the wrong naming scheme)

Aanok commented on 2018-11-29 14:19

Hello @Modelmat! Your PKGBUILD is set up to install all requirements through pip. On my machine this was creating some conflicts (in fact, it is generally discouraged in packaging guidelines), so I rewrote it to use Arch and AUR packages instead.

The two main drawbacks of this are that

  1. The maintainer must keep track of all upstream requirements manually;

  2. Requirements in the Python package have == on versions, which are very inconvenient to satisfy system-wide. My workaround has been a sed -i 's/==/>=/' requirements.txt, which works for now but eventually won't in the future.

In any case, I thought you or other people installing onedriveClient might find it of use, so here it is: https://pastebin.com/yMd806Ab

BTW, the sha256 checksum for the systemd unit file needs to be updated.