Arch Linux User Repository

@yochananmarqos Your PKGBULID is significantly different in a number of aspects. I'm not even entirely sure what the point of all the changes is, but I know that namcap is not giving us the same results. You do understand that we're punting and throwing away a large chuck of what would normally be built here and punting to the system electron instead of what would normally be bundled. Hence we don't need all the dependencies that Electron & electron-builder would normally want to see in a build scenario.

@caleb: Yes, I just ran namcap again just now after building in a clean chroot using my PKGBUILD.

Also fontconfig is listed as a dependency in the electron-builder.yml.

@yochananmarqos I'm not saying you're wrong here, but are you sure you ran namcap on a freshly built package using the current electron dependency? I think the fontconfig dependency is buried inside Electron and is not used directly by this app. After the latest update that uses the [community] electron package again I don't think that dependency should be needed, and running namcap on my build backs me up. Can you confirm — one or the other of us is doing something wrong.

fontconfig is a missing dependency:

marktext I: Link-level dependence (fontconfig) in file ['usr/lib/libfontconfig.so.1']

marktext I: Depends as namcap sees them: depends=(libsecret fontconfig libxkbfile)

Good news everyone. Since the upstream project has finally gotten up to speed with current Electron releases, as of the 0.16.3 release posted about an hour ago this build is back to working with the Arch [community] electron package. It also builds with any current nodejs package so you don't have to downgrade to an old LTS to build either.

If you don't want to build at all, as always the most recent successful build I've run is available in my user repository.

@kipsora Sorry for the confustion there, I did miss something. In the mean time while this package should work now I actually recommend using marktext-git because the upstream project has finally updated to use a real modern Electron (11) which can be supplied by the [community] packages again. This package will not reflet this until the 0.16.3 release, but the Git package already uses it (and that's what I'm actually running, which is why I didn't even notice this was only pretending on the Electron 8 bump).

Is the current building script corrupted? Well I can install electron8-bin as required but the PKGBUILD still uses electron7 for building stuffs.

@monoid What a fiasco! The electron7 package was dropped from [community] but there is an AUR package eletron7-bin that provides it. You can use that. This is actually available for 8 too and I didn't want to go down the road of using an AUR bin package, but there is less and less options available to us. I preferred the downgrade to 7 over the bin package. Now that our hand is forced I'll bump this to 8 again. People that want to build it can supply that how they want, but currently electron8-bin is the only way I know of.

If anybody submits a working electron8 source package to the [AUR] I'd be happy to build and host it in my package repository.

@caleb

electron7 seems to have been removed from the official repos. Not sure what would be the best course of action, maybe adding electron7 to AUR and using that instead?

Not much work has been done towards electron9 support just yet https://github.com/marktext/marktext/issues/2128

PKGBUILD using NVM to set the Node.js version during build instead of replacing nodejs with nodejs-lts-erbium on one's system.