Arch Linux User Repository

Good news, everyone!

After a brief exchange over a fairly long period of time with The Upstream Gods, the error that was preventing compilation has finally been fixed (it was just a silly node version mismatch in the instructions). I can now apply the fix so that this package will compile from source, thus complying with the AUR submission guidelines.

Unfortunately, I still need to implement it through a PKGBUILD, and this week I'm extremely busy. Since the update has been stalled for a long time, @drankinatty has persuaded me to post this temporary patch using the old method until I can push a proper fix.

I should be back in around a week with a definitive patch.

Best regards.

PS: Thanks again to drankinatty for providing the PKGBUILD

Well, no, the source is from mongosh-2.8.2.tgz, it uses npm during the build. I've already rebuilt this package but you locked me as co-maintainer out of the repository. That said, if you can build it without involving npm, that will be a significant security improvement. But the build process is really an "assemble" process where npm is used to assemble all the ~14,000 javascript and typescript source files together that make up mongosh in /usr/lib/node_modules/mongosh/.... (something that could have been done in 100k of a single compiled executable). Definitely a "Rube Goldberg" shell. I don't know the history of mongosh, but it looks like something originally envisioned to run as app in a browser. The Arch mongosh seems to only use about 10% of all the .js and .ts files that are pulled in to run as a command-line shell. I didn't see anything in the upstream repository that lets you reduce the components pulled in though.

If you want to update the package in its current form, you can update the PKGBUILD with:

pkgver=2.8.2
...
sha256sums=('05af84a971f55ff2b28e91dc7fbdfa7db4528fd9687d7da609e95a4a3ad4d431')

Good luck with your investigation on an alternative build to whittle some of the cruft from the package. This package is not simply a binary that is pulled in, it's the entire .js and .ts set of source files assembled together and run as a node.js application. The simple CLI could probably do without 80% of the source files, but I'm not a javascript/typescript/node developer, so how you would do that isn't something I can help with.

Hi all,

I've just taken over this package and I'd like to leave a progress report so as to inform everyone on what's going on and why this hasn't been updated yet.

Firstly, after examining the PKGBUILD, it seems the source is being pulled directly from the npm package. This counts as a binary, whereas this package is supposed to serve source contents. If you're still interested in downloading a binary version of this program, please refer to mongosh-bin, it's well maintained and it's exactly what you're looking for.

Next, I'd like to explain what's going on with the new update. I'm trying to modify the PKGBUILD so that it will actually use the latest source code release. Unfortunately, the upstream GitHub's instructions for compilation seem to be obsolete and I've not been able to find any workarounds. I posted a Jira ticket two weeks ago after I adopted the -git version of this package, but I still haven't heard anything from the devs. For now, the package will be left outdated until I get a response from upstream and then I'll decide how to proceed.

In the meantime, if anyone has any ideas to bring this up to date, please do contribute and don't hesitate to ask for co-maintenance should you be interested in implementing them directly.

Best regards.

pkgver=2.5.8
...
sha256sums=('2f9f60f72765044d9dac0728b1b38fb340b6142047af80f568f2b4baad5249fa')

Works fine.

pkgver=2.5.2
...
makedepends=(git npm modclean libmongocrypt python)
...
sha256sums=('2eb36d5562e8d4a7acad1253891ad1d733169e0dd6c19f91bc9db2b66045f9ad')

pkgver=2.3.9
...
sha256sums=('5d3ea533f1493615c96962500895e42cd42b303853cf2f72057a8da097981dd6')

pkgver=2.3.8
...
sha256sums=('80db9c5a5bab54e8a820661acc6ab0f89922fc68fe0400f718bfdc410b35f5fa')

Builds fine and works well with those changes.

pkgver=2.3.7
...
sha256sums=('eb95034ba700aa39bff573131bffeffeeb3e5af3e421ff35860fa24255921f9e')

pkgname=mongosh
pkgver=2.3.3
...
sha256sums=('52b9d71ee1026d515b1d86dd791f58eb6f45382c8e1ca85bb9b5601e38dc6d1c')

I think I have everything working as of now, I've changed to installing the package using npmjs.com's tarball instead of GitHub's and I'm not building deps from source until libmongocrypt#604 is merged.