Arch Linux User Repository

Please update to the latest version 1.21.

I have an updated fork that auto-generates the package.json so you often just need to update the pkgver. However, the script that does that is more complex than its output (and less straightforward to adapt if that should become necessary), so the maintainers are reluctant to rely on it. If you want to try it:

git remote add autofork https://gitlab.com/ccorn/arch-theia-electron.git
git fetch autofork
git switch autopackage

Please update to the latest version 1.21.

Upgrade to v1.17.2 is in the pipeline.

If you are impatient, cd into your checkout and do

git switch -c 1.17.2
git pull https://gitlab.com/ccorn/arch-theia-electron release/1.17.2

New update merge request there. Once merged, future upgrades should be as easy as for other packages because the tedious legwork has been automated now.

I have filed a merge request to upgrade this AUR package to 1.17.0. However, the resulting theia-electron application has a quirk (showing a welcome screen instead of immediately resuming the most recent session) that I would like to see fixed first. If you are willing to look into that, git fetch the release/1.17.0 branch and play with it.

Was trying to build it in chroot, throws error about package.json not passing validity check. Compared the values in PKGBUILD and md5sum of package.json and they turned out to be different. After fixing the value in PKGBUILD, everything went smooth afterwards.

• md5sum of package.json aca0c5da32944e7a9dd519304a362bc6
• md5 in PKGBUILD b167f5bf37cad01957c0720ab4dc2a79

@bence.hornak: Thanks for the link to the upgrade guide. I have updated the dependencies accordingly. This has resulted in the addition of @theia/plugin (though that one seems to be pulled in by dependency resolution anyway) and @theia/plugin-metrics.

I have made a merge request for the upgrade.

I am not interested in co-maintainership because I'd have to know more about NodeJS before messing with such stuff on a regular basis.

Hey @ccorn, thanks for the comment.

You can find our recipe with @Leon0402 here: https://gitlab.com/bencehornak/arch-theia-electron/-/wikis/Upgrade-guide

We are more than happy to accept contributions in the GitLab repo, or PM me, if you are interested in co-maintaining the package.

For those who want to upgrade to the current release version without having to wait for an AUR update, the main problem will be to adapt the package.json file bundled with the PKGBUILD.

Here is what I have done to adapt the package.json. Note that I am not familiar with the NodeJS ecosystem, so I downloaded the Theia release tarballs for 1.12.0 and 1.14.0 and tried to figure out where the specs in the package.json come from. There is no in-depth understanding behind this, so I may have overlooked or misunderstood something. The result works however.

1. Download a recent Theia release theia-X.XX.X.tar.gz and unpack it
2. Update the following fields in the AUR's package.json
   • from theia-X.XX.X/package.json
     • dictionary theiaPlugins (to update plugin versions, see below)
   • from theia-X.XX.X/examples/electron/package.json
     • string version
     • dictionary dependencies
       • without @theia/api-samples (would not be found)
     • dictionary devDependencies
3. The Theia release tarball (and the tree extracted from it) are no longer needed.

4. The plugin versions copied from the upstream package.json file tend to be outdated. The AUR package.json used to specify updated versions instead.

   To find updated version specs of all plugins in ready-to-paste form, use the following bash pipe (starring curl, jq, and sed):

jq -r '.theiaPlugins|to_entries[]
| (.key|@json) + "\t" + (.value|split("/")|.[:6]|join("/"))' \
package.json | (IFS=$'\t'
while read -r plugin url; do
  vurl=$(curl -LsS "$url" | jq '.files.download')
  printf '    %s: %s,\n' "$plugin" "$vurl"
done) | sed '$s:,$::'

That's it. In the PKGBUILD, update pkgver and the checksum of package.json.

You can remove most packages from makedepends. Only with makedepends=('yarn' 'node-gyp'), in a clean chroot environment, the app was built successfully.