Hi, I'm looking for uploading moolticute[0] into AUR but I still have some doubt that my package has good taste or not. The project is in C++ and use qt-5. I would like to upload a classical PKGBUILD[1] (with tag release) then one that follow the git master branch[2]. As the daemon is expected to talk with an USB device I included an udev rules that should match it and allow logged user interaction. In addition, the project does not include any systemd service file. The daemon is expected to run for every user session so I use systemd user instance. This service file is now very basic I will first try to make it upstream, so every distribution could benefit from this eventually. I guess that a lot are using systemd now. While creating the systemd file I was wonderering how would be the guideline in a case that an upstream systemd service file won't match (for any reason) Arch Linux policy (let say applying it will break the package functionality in Arch) would the good way to fix it in the first would be to create in the PKGBUILD a systemd drop-ins? Regarding udev, after installing my rule I decided to force reloading the rules files but not replaying event (only print a message to warn the user). My view is that the later would only be needed for people that already plugged the device before installing the package. Even with the i686 phase out, the tools seems to work great with this architecture, so I included it too. Finally, the release name[3] currently include "beta" (like v0.5.2-beta) does I have to put this into the pkgver or leave as 0.5.2? If comments/directions I will be glad to improve my work. Thanks ! [0] https://github.com/raoulh/moolticute [1] https://git.bourgeois.eu/aur_moolticute.git/tree/PKGBUILD?id=85e4d6f29352a54... [2] https://git.bourgeois.eu/aur_moolticute_git.git/tree/PKGBUILD?id=140f3e3efce... [3] https://github.com/raoulh/moolticute/releases