Arch Linux User Repository

WARNING: Lens has closed its source code

Lens has officially become a closed source application so this package will no longer be updated and may soon request to be removed from the AUR.

If you are interested in continuing to use Lens you can use the lens-bin binary package or, better, use an open source alternative such as k9s, kdash, Headlamp or Seabird.

Here is the image I created to build my packages. I'll try your script and compare the steps.

https://github.com/zaggash/docker-makepkg

That's a good idea, I just tried it in a container as well. Unfortunately I haven't gotten that error yet, but here's the script I used in case you want to compare notes:

#!/bin/sh

set -o errexit

trap "docker rm --force lens-build" EXIT

docker pull archlinux

docker run \
  --detach \
  --name lens-build \
  archlinux \
  sleep infinity

docker exec -i lens-build bash <<-EOF
  set -o verbose

  pacman -Sy --noconfirm \
    base-devel \
    git \
    nodejs-lts-erbium \
    node-gyp \
    yarn

  useradd --create-home testuser
  echo "testuser ALL=(ALL) NOPASSWD:ALL" > /etc/sudoers.d/testuser
  su - testuser

  git clone https://aur.archlinux.org/lens.git
  cd lens
  makepkg -si --noconfirm
EOF

I tried to build it interactively and did an echo $NODE_ENV It return nothing, there is no such variable.

I even tried to set it to export NODE_ENV=development

Same result.

I'm actually building my AUR package on my CI setup in Docker. Hence I have fresh archlinux install everytime using archlinux as a base image.

Here are the command I run to build:

this install all the needed dependencies

yay -Sy --noconfirm $(pacman --deptest $(source ./PKGBUILD && echo ${depends[@]} ${checkdepends[@]} ${makedepends[@]}))

this trigger the actual AUR build

makepkg -f

Let me check the variable.

I'm having trouble reproducing your issues. Looks like concurrently is a devDependency, so I'm not sure why it wouldn't be available after the yarn install step.

Does echo $NODE_ENV return anything? If that were set to production, then I could see why the dev dependencies wouldn't install.

yarn install --frozen-lockfile
yarn download-bins
yarn run v1.22.5
yarn install v1.22.5
$ concurrently yarn:download:*
/bin/sh: concurrently: orden no encontrada
error Command failed with exit code 127.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
make: *** [Makefile:13: download-bins] Error 127

Hello.

During my build, I have the follwing issue.

[...]
yarn install v1.22.5
$ concurrently yarn:download:*
/bin/sh: concurrently: command not found
error Command failed with exit code 127.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
make: *** [Makefile:13: download-bins] Error 127
make: *** Waiting for unfinished jobs....
[...]

Any ideas ?

EDIT: I assume concurrently and ts-node should be installed during the build process. So npm should be part of the make dependencies. Unless there is another way I didn't pay attention.

Thanks Sacro, just made some changes:

I found the "$pkgdir"/usr/bin was needed, but the path was wrong and creating an empty folder.

I also fixed the linking to the installation folder. I took a look at another package, and saw that they link to /opt directly, so I did that.

Thanks for bring these up.

install -d "$pkgdir"/usr/bin/$pkgname

not sure why this is needed, seems to create an empty folder

ln -s "$pkgdir"/opt/$pkgname/kontena-lens "$pkgdir"/usr/bin/

this links to the build folder, not the install folder.

ln -s ../../opt/$pkgname/kontena-lens "$pkgdir"/usr/bin/

fixes it