VCS package check - chuncord-git
Hello, I just want some quick feedback on a package I made a few days ago, this was my first time writing a VCS package, so I want to make sure I have done everything properly: https://aur.archlinux.org/packages/chuncord-git Please let me know if I have done anything wrong. Thank you, -- Polarian GPG signature: 0770E5312238C760 Website: https://polarian.dev JID/XMPP: polarian@polarian.dev
Jun 9, 2023 09:28:06 Polarian <polarian@polarian.dev>:
Hello,
I just want some quick feedback on a package I made a few days ago, this was my first time writing a VCS package, so I want to make sure I have done everything properly:
https://aur.archlinux.org/packages/chuncord-git
Please let me know if I have done anything wrong.
Thank you, -- Polarian GPG signature: 0770E5312238C760 Website: https://polarian.dev JID/XMPP: polarian@polarian.dev If you're doing the whole "export rust envvars" thing, you'll also want to add "*export RUSTUP_TOOLCHAIN=stable*" to the top of prepare() [1].
pkgdesc should also be at most 80 characters [2]. VCS part looks ok to me. - éclairevoyant [1]: https://wiki.archlinux.org/title/Rust_package_guidelines#Prepare [2]: https://wiki.archlinux.org/title/Arch_package_guidelines#Package_etiquette
Hello, Thanks for pointing out the fact I forgot the export in prepare(). Also I rarely check the length of descriptions hence why this one is longer, I will check for now on but it is only a guideline, surely its better to be accurate than be rigid on 80 characters only? I am sure I can strip it down to 80 characters, but my point is for future reference what if the description cant be stripped down to 80? Thanks for the help, -- Polarian GPG signature: 0770E5312238C760 Website: https://polarian.dev JID/XMPP: polarian@polarian.dev
participants (2)
-
Polarian
-
é