Arch Linux User Repository

Thank you dosenpils and masterkorp for supporting the package.

I replaced the PKGBUILD with the version I wrote for the archlinuxcn repo. I will do my best to follow the latest electron versions.

Please try to build in a clean chroot (i.e., with extra-x86_64-build from devtools package) if you have problems building the package.

If you want to use the fcitx input method under wayland, please complete the following configuration:

cat .config/electron25-flags.conf 
--enable-wayland-ime
--ozone-platform=wayland

it all began, with you assuming Manjaro shouldn't be broken

It began with me explaining it's not a bug, it's a Manjaro feature.

@meyznu, Yes, corepack really was unexpected for me as well. Luckily installing it and the dependencies for it on a modern Manjaro installation works. I hope Manjaro catches up soon. :)

This latest update introduced the dependency corepack because the package doesn't build on Arch Linux anymore without it

Got it. Thank you!

"if your changes didn't break Manjaro?" <-- That's where

Explain to me how this can be interpreted as a demand. It's my honest opinion. Maybe there is something wrong with my English. I will change my English for you in the future.

@meyznu, "if your changes didn't break Manjaro?" <-- That's where (edit:) it all began, with you assuming Manjaro shouldn't be broken. And you can blame Manjaro for lagging behind, since it's not Arch's responsibility or this package's maintainer to hold Manjaro up. They don't have to lend themselves to Manjaro users or missions, in any way, that's just called entitlement. Edit: I say this all, AS SOMEONE THAT MAINTAINS MANJARO INSTALLATIONS. I also maintain packages on the AUR for Arch primarily, Manjaro secondarily since the point of the AUR is to be the AUR. ARCH user repository. ARCH. Edit: I won't be responding any further with you on this issue. Take a step back and remember the AUR is not even for Manjaro users.

It's Manjaro that needs to catch up. The only current way for Manjaro users would be for them to download the Arch repo ZSTs (or clone and build them) until Manjaro catches up to the corepack separation. There's nothing to re-work in the package.

@OdinVex Where did I demand anything? On the contrary, I said "it's totally up to you". I expressed my personal opinion, which I am entitled to. I didn't switch to ad hominem, either. So, what's the problem?

Blame Manjaro

Manjaro is trying to do something good by putting more QA. Why would I blame it for it?

@meyznu OK, let's try to be more constructive. This latest update introduced the dependency corepack because the package doesn't build on Arch Linux anymore without it, as some users reported earlier. I'm OK to introduce trivial fixes for Manjaro but I don't see an obvious one. Do you have any suggestion? The bottom line is it has to work on Arch Linux, even at the expense of breaking the compatibility with other distros.

@meyznu, You're still blaming the maintainer as if they broke something. It's Manjaro that hasn't updated to using corepack yet. Blame Manjaro, not the maintainer.

I'm upset. My weekend mood is ruined. Whatever. I'm not going to extend this thread.

I'm sorry I upset you. Let me try to reframe my message in a positive way. We all here love Linux, especially Arch Linux. Wouldn't we all want more people to use Arch Linux? Manjaro distro tries to do it and extend our love for Arch to less experienced users by putting more QA effort into it. Wouldn't it be wonderful and serve the greater good if your changes didn't break Manjaro? What do you think?