Package Details: wechat 4.0.1.11-1

Git Clone URL: https://aur.archlinux.org/wechat.git (read-only, click to copy)
Package Base: wechat
Description: 微信是一种生活方式. This is a repackage of the official WeChat which includes an optional sandbox support
Upstream URL: https://weixin.qq.com/
Keywords: binary qt sandbox universal wechat
Licenses: LicenseRef-Proprietary
Conflicts: wechat-bin, wechat-universal, wechat-uos
Provides: wechat-bin, wechat-universal, wechat-uos
Replaces: wechat-bin
Submitter: Kimiblock
Maintainer: Kimiblock
Last Packager: Kimiblock
Votes: 51
Popularity: 12.60
First Submitted: 2024-06-30 11:27 (UTC)
Last Updated: 2024-12-26 11:04 (UTC)

Dependencies (43)

Required by (1)

Sources (6)

Pinned Comments

Kimiblock commented on 2024-12-27 07:34 (UTC)

若遇到输入法, HiDPI 等问题, 请安装 wechat-bwrap 附加包

Kimiblock commented on 2024-12-26 08:49 (UTC)

若要启用沙盒, 请安装 wechat-bwrap.

请在发表评论时检查事实, 使用正常语言.

Kimiblock commented on 2024-11-13 11:11 (UTC) (edited on 2024-12-11 08:01 (UTC) by Kimiblock)

分享文档时, 请先将📃放入数据目录: 右键应用程序图标, 选择 Open WeChat Data 或手动打开 "${XDG_DATA_HOME}"/WeChat_Data (默认为 ~/.local/share/WeChat_Data), 微信会将这个目录作为家目录.

WeChat_Data/portable.env 中的环境变量将会自动导入至微信.

不支持纯 Wayland 环境, 微信并未构建 Wayland 模块.

Kimiblock commented on 2024-11-13 11:09 (UTC)

若要查看使用手册, 访问 https://wiki.archlinuxcn.org/wiki/WeChat

For user manual and internal document, consult https://wiki.archlinux.org/title/WeChat

st0ne commented on 2024-07-27 16:00 (UTC) (edited on 2024-07-31 04:35 (UTC) by st0ne)

KDE Plasma 添加阴影

1.添加阴影

在微信界面，ALT+F3 -> 更多操作 -> 配置特殊窗口设置 -> 添加属性 -> 添加 外观和修正 下面的 无标题栏和边框 -> 将 初始状态应用 改为 强制，将后面的 是 切换称 否 -> 应用

2.去除标题栏

之后微信就有边框阴影了，但是微信多了个标题栏。

设置 -> 颜色和主题 -> 窗口装饰元素 -> 找到你在用的主题右下角的编辑 -> 切换到 特定窗口优先规则 -> 添加 -> 检测窗口属性... -> 选中微信窗口 直到 匹配正则表达式 那里出现 wechat -> 勾选 装饰选项 下面的 隐藏窗口标题栏 -> 确定 -> 应用

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 .. 51 Next › Last »

Kimiblock commented on 2024-12-07 17:35 (UTC) (edited on 2024-12-08 02:27 (UTC) by Kimiblock)

Then I wonder why months have passed with little to no progress. 🤔

I'd imagine it's not something like pretending that we did push the progress and call it a day.

Antiz commented on 2024-12-07 17:22 (UTC) (edited on 2024-12-07 17:32 (UTC) by Antiz)

@Kimiblock This indeed is an inappropriate usage of the "replaces" array. This should be a "conflicts" array at best.

As you know (since you started the related discussion on the ML), the "wechat packaging situation" in the AUR is a bit controversial and difficult to deal with.
Claiming legitimacy over the other existing packages in a forced and unexpected manner like you're doing is not helpful.

I switched the "replaces" array to a "conflicts" one, please do not switch it back and give time for the AUR staff to deal with the pending requests about wechat related packages.

Thanks for your comprehension & collaboration.

Kimiblock commented on 2024-12-07 16:45 (UTC)

If you have any more concerns, contact me via mail.

Do not flood this area with useless comments.

Kimiblock commented on 2024-12-07 16:44 (UTC) (edited on 2024-12-07 16:51 (UTC) by Kimiblock)

Are you failing to catch my point again and again, or intentionally done just to define me as a rule breaker?

I do not want to be a repeater and replace is allowed when a package is subject to rename (merge)

envolution commented on 2024-12-07 16:31 (UTC)

@kimiblock to be clear, you're refusing to follow the AUR guidelines? You are also confusing replaces with conflicts.

Currently this package is maliciously replacing packages you want merged where other maintainers disagree.

Kimiblock commented on 2024-12-07 16:24 (UTC) (edited on 2024-12-07 16:26 (UTC) by Kimiblock)

@envolution I don’t think AUR helpers have the ability to replace packages yet. And you are avoiding the duplication fact.

Replaces here only stands as a statement that dupes should not be allowed and has no actual effect.

I should follow the guidelines only when others do. Or I see this as a double standard.

envolution commented on 2024-12-07 16:05 (UTC)

@Kimiblock The job of an AUR maintainer is not to force external packages to uninstall and be replaced by your own. If you cannot follow the guidelines, perhaps you are not a good fit for the task.

The guidelines are very clear for this exact reason.

Kimiblock commented on 2024-12-07 15:57 (UTC)

Sadly I’ve got in touch with the maintainer of wechat-bin and his not willing to merge for unknown reasons

Kimiblock commented on 2024-12-07 15:56 (UTC)

@envolution u didn’t read what I replied, did you?

The history of WeChat packaging on AUR is controversial after Tencent released the Qt new version. wechat-uos-bwrap was the first to package this Qt version. Later it renamed to wechat-uos-qt and wechat respectively. Other packages didn’t follow the AUR submission guidelines in the first place by duplicating existing package and I’ve already discussed this with fellow maintainers in the mailing list. Of which you can check it out at https://lists.archlinux.org/hyperkitty/list/aur-general@lists.archlinux.org/thread/T4I2ZYPOPHTIKYJTUSB7CMHSNA6BHIZ7/.

Thanks for your effort to keep AUR community in line with the guidelines. I wish you can understand the rationale behind this.

envolution commented on 2024-12-07 15:38 (UTC)

@kimiblock Please follow the AUR submission guidelines, you are using "replaces" maliciously.

« First ‹ Previous 1 2 3 4 5 6 7 8 9 .. 51 Next › Last »