I couldn't figure out how to build either. I created an issue here: https://github.com/lando/lando/issues/3052
Luckily, the devs were kind enough to release a .deb so I created a new lando-bin PKGBUILD. https://aur.archlinux.org/packages/lando-bin/
Git Clone URL: | https://aur.archlinux.org/lando-git.git (read-only, click to copy) |
---|---|
Package Base: | lando-git |
Description: | A free, open source, cross-platform, local development environment and DevOps tool built on Docker container technology |
Upstream URL: | https://docs.devwithlando.io |
Licenses: | GPL |
Conflicts: | lando |
Provides: | lando |
Submitter: | dmp1ce |
Maintainer: | None |
Last Packager: | dmp1ce |
Votes: | 2 |
Popularity: | 0.000000 |
First Submitted: | 2018-11-24 01:32 (UTC) |
Last Updated: | 2020-03-23 12:56 (UTC) |
I couldn't figure out how to build either. I created an issue here: https://github.com/lando/lando/issues/3052
Luckily, the devs were kind enough to release a .deb so I created a new lando-bin PKGBUILD. https://aur.archlinux.org/packages/lando-bin/
@dmp1ce It seems that lando has changed their build process which is causing this package to fail building. Their documentation still references the npm script "pkg:cli" but it no longer exists.
@dmp1ce Sorry, that was my bad. Yay couln't make heads or tails of it. Actually performing the build did just install 3.0.19.r2 as it is supposed to.
Building should result in at least lando-git-3.0.19.r2 currently. The package was flagged, but from what I can tell, nothing is wrong.
ElijahLynn: The -git build takes the latest version from git and builds it. rrc.2 works fine for me.
Can you update to v3.0.0-rrc.2 please (latest release, 8 days ago)
Supposedly aft is "almost fu****g there".
Why is upstream making all the weird release labels? What is "aft" and "rrc"?
1 more update pls? :)
Can you please update.
please update to rc.19
Here is the issue I see currently. https://github.com/lando/lando/issues/1297
Also, I need to find a way to build with an older version of npm because of build requirements.
I'm not sure if lando is useless without docker-compose but it probably is. Maybe they have different backends for lando. I mostly removed it as a hard dependency because namcap said docker wasn't a dependency.
Simply running yarn didn't work for me. I would prefer to only run yarn if it worked without any errors.
More importantly, I'm not sure if lando works with the latest version of docker-compose anyway. Once I can do some more testing I'm going to report that issue I'm having too.
@dmp1ce
But isn't the tool pretty useless without either of those? I'm newish to arch so correct me if I am wrong with this assumption?
Usually you just run "yarn" to install the packages as defined in the lock file? Perhaps wait till they reply to see what's correct.
@inverse, I didn't think docker or docker-compose needed to run. In order for it to manage the environment docker and docker-compose is of course needed and many commands will fail.
I could only get things to work by updating npm packages. I raised an issue here: https://github.com/lando/lando/issues/1309
What should be done here? Maybe patch the yarn lock and only use yarn?
Thanks for making this. Some feedback.
Pinned Comments
dmp1ce commented on 2021-06-17 20:37 (UTC)
I couldn't figure out how to build either. I created an issue here: https://github.com/lando/lando/issues/3052
Luckily, the devs were kind enough to release a .deb so I created a new lando-bin PKGBUILD. https://aur.archlinux.org/packages/lando-bin/