Arch Linux User Repository

@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.

With both Markdown extensions packaged, you get two "preview" icons in the tab header for markdown files, one of which does not work, and a log message about initialization failure of the extension Markdown Language Features (built-in):

n.Window.registerCustomEditorProvider is not a function

I have therefore removed the line for vscode-builtin-markdown-language-features from package.json in my checkout. Now there is only one preview icon, and it works.

The upstream has released a deb package built by CI, is anyone interested in creating a theia-electron-bin package? https://github.com/eclipse-theia/theia/issues/5481#issuecomment-709526924

The symlink can also be dereferenced with cps -H option. Thus you do not need to specify an install command with strange (executable) permission flags:

--- a/PKGBUILD
+++ b/PKGBUILD
@@ -46,15 +46,12 @@ package() {
   # Create directory
   install -dm 755 "$pkgdir"/usr/lib/$pkgname

-  # Source code (symlinks are not dereferenced) and plugins
-  cp -r --no-preserve=ownership --preserve=mode \
-      src-gen lib node_modules \
+  # Source code (command-line symlinks dereferenced) and plugins
+  cp -RH --no-preserve=ownership --preserve=mode \
+      src-gen lib node_modules package.json \
       plugins \
       "$pkgdir/usr/lib/$pkgname/"

-  # package.json
-  install -Dm755 package.json "$pkgdir/usr/lib/$pkgname/"
-
   # Executable
   install -Dm755 theia-electron.sh "$pkgdir/usr/bin/$pkgname"
   # Desktop file

Hi @Leon0402, You are right on the StartupWMClass, I changed it to electron. The failing build issue should also be eliminated, see https://gitlab.com/bencehornak/arch-theia-electron/-/issues/1.

Hi, thanks for the package!

The theia-electron.desktop file is not quite correct or at least not matching the application. xprop showed that StartupWMClass should be electron rather than theia. Otherwise the window will not map correctly and it will use a fallback icon and not work properly with the task manager. I believe though, that actually the fix should rather be done somehwere else, so the WM Class is theia. But I don't know where this should be done.

Furthermore, the package doesn't work out of the box with the aur helper pikaur. The package seems to build on the fact that cache is preservered during build. Therfore: pikaur -S theia-electron --keepbuild was necessary

Okay, I updated the PKGBUILD