[aur-general] 回复： Request to check my PKGBUILD

[悲剧小白]

1.The AppRun file specifies the location of some lib files of the software. These variables seem to be called when the software is running.


2.The purpose of "chmod -R 755" is to change the permissions of these folders, but it also affects the pictures in the final directory, so use "chmod 644" to change the permissions of the pictures back.
If you do not change the permissions of these folders, their permissions in the source directory are 600, and a warning will be output during installation that the directory permissions in the installation package are inconsistent with the permissions in the file system (In a clean ArchLinux environment, the default permission of the /usr/share/icons folder is 755)


Finally, please point out where I did not use $pkgdir correctly, I will check again


------------------ 原始邮件 ------------------
发件人:                                                                                                                        "Discussion about the Arch User Repository (AUR)"                                                                                    <aur-general at lists.archlinux.org>;
发送时间: 2021年7月13日(星期二) 中午12:21
收件人: "aur-general"<aur-general at lists.archlinux.org>;
抄送: "Eli Schwartz"<eschwartz at archlinux.org>;
主题: Re: [aur-general] Request to check my PKGBUILD



On 7/12/21 11:50 PM, 悲剧小白 via aur-general wrote:
> I made a PKGBUILD for the "Badlion Client" software, but there will
> be some warnings during the build. How can I deal with this problem?
> If PKGBUILD has any other questions, please let me know.
> 
> tips: Badlion Client is a third-party launcher for Minecraft games.
> To run the game, you need to have a genuine Minecraft Java Edition
> account.

Hmm, what's the purpose of replacing the AppRun script? In fact, why not
just run the binary directly?

Also I notice in your PKGBUILD you chmod -R 755 a directory tree... you
should probably not be marking the files inside there, as executable.
They're just images. Why do you them chmod -R 644 some of the files?

Maybe you should consider using:

chmod -R ugo+rwX

(Also: this once, you forgot to quote $pkgdir correctly.)


-- 
Eli Schwartz
Bug Wrangler and Trusted User