Hello, I wrote this PKGBUILD at 4am in the morning, I am an idiot. /etc/ is normally always root, I do not see why gitea changes this but who cares because as long as the configuration is readable by the uberbot user, it would work, however this does prevent the application modifying its own configuration. But I assume if you needed write permissions you would give uberbot ownership of only the configuration file within the directory, instead of the directly completely (you probably dont want having write access to a directory in /etc/ to be honest). So yes actually thinking it through a little more, and also abiding by the concept of "least permissions", this was a stupid way of doing it, I can simply change the install command to include -g and then 664 to allow uberbot to still read the config, but not write to it (it doesn't need to write to it and thus that permission is not required!). As for the incorrect use of tmpfiles, this is solely a lack of experience as I rarely need to use them. I have read the man pages but my brain is like a bucket with a hole in the bottom, so thats for pointing the 'd' line out.
It's missing dependency on gcc-libs.
I do not see this mentioned within the package guidelines, but I did find it as a dependency of ripgrep (one of the example packages). Mind explaining why rust needs compiler libraries at runtime? (I don't like doing something until I understand why it must be done, I hope you understand)
* It needs options=(!lto) since it won't build with LTO on and the default linker. (I guess you can also force a different linker that works.)
Again not mentioned in the rust package guidelines, but I believe rust does LTO itself, and thus you do not want makepkg from interfering, correct? If these are well known "conventions" of sorts for rust packages, why is it not in the guidelines? Looking at the rust guidelines I see there is a lot of controversy over them, some values "being redundant". Email:
Not sure if you fixed your package() already but there were some errors with the install cmds...
I do not believe they were specifically "errors", but stripping the -t flag out does make the package() function easier to read and maintain. The current package() function does actually work just fine, all files are installed to the right directories and have the right permissions but the suggestion you gave is a lot nicer.
Also I would suggest to put the config.toml in the backup-array so it doesn't get overwritten by pacman on updates!
Yeah I planned to do that, but I was more worried about getting it to work first, then worrying about the small things :P Thanks for the reminder on it though :) Thanks for the help, -- Polarian GPG signature: 0770E5312238C760 Website: https://polarian.dev JID/XMPP: polarian@polarian.dev