Package Details: outrun-git r3.1e86c42-1

Git Clone URL: https://aur.archlinux.org/outrun-git.git (read-only, click to copy)
Package Base: outrun-git
Description: Execute a local command using the processing power of another Linux machine
Upstream URL: https://github.com/Overv/outrun
Licenses: Apache
Conflicts: outrun
Provides: outrun=r3.1e86c42
Submitter: xiretza
Maintainer: xiretza
Last Packager: xiretza
Votes: 0
Popularity: 0.000000
First Submitted: 2021-03-18 23:51
Last Updated: 2021-03-18 23:51

Latest Comments

m040601 commented on 2021-03-20 12:15

In case someone else is also wondering why vagrant is (optionally) "needed"

Silly me, just sat down and took some time to carefully go through the README https://github.com/Overv/outrun :

... outrun depends on OS interaction
... tests that simulate usage with a VM connecting to another VM
... using Vagrant...

Also, a correction to my previous claim about arm/raspberry.

Since the software to be executed is copied from your own machine to the remote machine, it must be binary compatible. It’s not possible to set up a session from an x86 machine to an ARM machine, for example.

So I cant use it as I had previously thought with my arm raspberries. Maybe later, with other extra binary compatiblity tool like qemu/arm/binfmt etc. Related issue, https://github.com/Overv/outrun/issues/11

m040601 commented on 2021-03-20 11:38

@xiretza

vagrant is in checkdepends

Thanks ! Ahhh, the "check" dependencies. I had missed that one.

...if you don't want to test the built package use makepkg --nocheck.

That's the really important thing here. Not using it alone will avoid having to pull gigabytes of ruby, gems, vagrant and go. Ufff :-)

xiretza commented on 2021-03-20 10:57

@m040601: there really aren't very many dependencies (only 8 runtime deps), and all of them are in the repos - I don't really see much of a problem here.

Edit after your edit:

  • vagrant is in checkdepends, if you don't want to test the built package use makepkg --nocheck.

  • makepkg will automatically uninstall make-/checkdepends after build with -r/--rmdeps

  • if you want to keep your system clean, build in a chroot using makechrootpkg, this will not install any packages on your host system.

m040601 commented on 2021-03-20 10:49

Thanks for making this PGKBUILD. A question about it's required dependencies.

I'm not familiar with python and have only a superficial knowldege of making PKGBUILDSso please forgive my ignorance.

I saw this announced on Hacker News, and then was happy to find someone had already made this PKGBUILD for Archlinux.

I was just about to install it when I saw the huge amount of dependencies and build dependencies. Both from the AUR as well from official packgage.

[Repo:16]  libpgm-5.3.128-1  zeromq-4.3.3-2  python-nose-1.3.7-10  python-tornado-6.1.0-3  python-iniconfig-1.1.1-1  python-more-itertools-8.6.0-3  python-pluggy-0.13.1-4  python-apipkg-1.5-5  python-py-1.10.0-1  python-pytest-6.2.2-1  cython-0.29.22-1  python-pyzmq-20.0.0-1  python-monotonic-1.5-7  python-fasteners-0.15-5  python-semver-2.13.0-3  fuse3-3.10.2-1
[Repo Make:8]  python-coverage-5.5-1  python-pytest-cov-2.11.1-1  rubygems-3.2.13-1  ruby-reline-0.2.4-1  ruby-irb-1.3.4-1  ruby-2.7.2-1  go-2:1.16.2-1  python-vagrant-0.5.15-5
[Aur:1]  outrun-git-r3.1e86c42-1
[Aur Make:1]  vagrant-git-2.2.6.203.ga1abc177b-1

Wow !!! That's huge.

Pulls python-vagrant, which pulls vagrant wich pulls ruby and ruby gems etc. It even pulls go, half a gigabyte. This is of course on my system, which I want to keep as lean as possible. I know most of them are make/build dependencies, and that I can remove them after the package is installed. I also know that I can do this build in a separated/isolated part of my system (build chroot, venv, pipx etc) to keep my main system clean. But still ... I don't want this, just to quickly test out a package.

So my question is:

  1. Is this absolutelly necessary ? Could some part of it be made optional ?
  2. Is their no way to make this (or another alternative PKGBUILD) to test "outrun" tool with a more lean package with less mandatory dependencies.

The only thing I could figure out was to inpect and check this: these sources

the requirement of the file "setup.py" on https://github.com/Overv/outrun/blob/master/setup.py , where there is this mention of "requires" and "extras requires" :

install_requires = [
    "msgpack>=1.0.0",
    "pyzmq>=19.0.0",
    "lz4>=3.0.2",
    "fasteners>=0.15",
    "semver>=2.9.1",
]

extras_require = {
    "dev": [
        "rope>=0.14.0",
        "flake8>=3.7.9",
        "flake8-docstrings>=1.5.0",
        "flake8-import-order>=0.18.1",
        "black>=19.10b0",
        "pylint>=2.4.4",
        "mypy>=0.770",
        "pytest>=5.4.1",
        "pytest-cov>=2.8.1",
        "python-vagrant>=0.5.15",
    ]
}

This is what ends up in the file "outrun.egg-info/requires.txt" on https://pypi.org/project/outrun/#files used by "pip install outrun"

Again, I'm not saying or demanding it should be done other than the way it is. I'm just wondering and asking.

The good reason for asking this is that "outrun" needs to be installed in 2 computers. I wanted to test this in a setup with a beefy machine talking to other less powerfull machines like my Raspberry Pi's or other arm chromebooks. They all run Archlinux or ArchlinuxARM. But, I dont' want to install go, rust, ruby etc on the tiny Raspberry Pi's.

Thanks in advance