feat: Adding Arch Linux package generation - #2627
Conversation
Still a WIP locally using `nektos/act`, pushing these changes in the meantime.
|
Still a WIP - I've been testing the GitHub Actions build locally using nektos/act - to hopefully get faster feedback on the workflow build/package process loop. What I hoped would be a weekend project turned out to be a little bigger. I've run into some challenges b/c it uses containers that are run as root. I can clean up my changes and provide my config changes to the workflow |
…ging-scripts/master
|
I was able to get the package to build properly locally within using nektos/act! I believe that GH actions are run as a non-root user, so this shouldn't be an issue. However, if it is, I should be able to address it quickly. |
After testing GH Actions in my own fork, I confirmed that it is indeed run as a root user.
|
Confirmed works 💯 locally w/ ACT and using the action runners on my fork! |
This is unnessesary (for now). If it's desired to test run GH actions locally with nektos/act, it will be re-added along with other changes/checks to run it locally.
|
I have confirmed the actions changes will run - I didn't think to link to it here I have downloaded the package and installed it & it's running on my machine. 👇👇👇 
|
As an Omarchy Linux user, I wanted to provide a means to generate Arch Linux package on releases. I'm hoping this may alleviate AUR package maintainers of some manual steps to re-release the package for Arch based distributions. Additionally, with recent supply chain attacks focused on AUR, I hope this would alleviate any worry about any malicious activity.