-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add PKGBUILD and publish Arch Linux package? #11
Comments
It should certainly be possible to adapt the PKGBUILD, and as i am using Arch Linux myself, i have some interest in a PKBUILD but have been to lazy and frustrated with the documentation to get it done (the mouse_m908 PKBUILD was done by someone else). For the My suggestion would be that you open a pull request with the PKBUILD you have been able to implement so i can have a look at it as well and merge it as soon as we get it to work. For publication on the AUR i will have to read the documentation, but that would obviously be the next step. |
I managed to use the mouse_m908 PKBUILD as a template and have added an experimental PKBUILD for the git version to the master branch. It works for me but is ugly in some places, and i would like to hear your feedback (and potentially improve it) before adding it to the AUR. Edit: you are obviously still welcome to open a PR with an improved version. |
I think I'll send a pull request which fixes your PKGBUILD; there's enough problems that it's easier to send a PR than a list of changes to apply. Also the filename is spelled wrong. EDIT: Who should push the package, and who do you want listed as a PKGBUILD maintainer? |
Yes, please do that, writing stuff at 3am tends to give results that are far from ideal.
I have no final opinion on that, what are your thoughts? |
I think I've spent more time researching the Arch guides and talking on the Matrix room about "proper" PKGBUILD format, but I don't think I'm going to maintain the package indefinitely. Maybe I'll try to document my understanding and let you submit it, or I could submit it and orphan it if I stop using rgb_keyboard. Do you prefer the package name |
Then i would suggest that you open a PR and i will submit it to the AUR as that gives me the opportunity to submit the mouse_m908 one as well. I prefer Edit: i would obviously be very thankful about any documentation that you can provide. |
https://wiki.archlinux.org/index.php/AUR_submission_guidelines#Rules_of_submission says the PKGBUILD comments should contain the maintainer's contact info. What's your email? I don't think I should list EDIT: Alternatively I can send the PKGBUILD in this issue and you can fill out the rest. |
Please add the PKGBUILD to this issue or as a PR to the main repo, i will have to create an account on AUR first and maybe a new email adress and add my info then. But that has to wait until i've slept (no need for new stupid mistakes on my side). |
PKGBUILD is at https://gist.github.com/nyanpasu64/52a05e53da220b299e6ba99fb1c229dc, you'll have to fill in your email yourself. I tested that it installs properly. ObservationsAccording to the Arch wiki, you're better off basing PKGBUILDs off templates in the example folder. Because this is a Git package, I used (Also you spelled PKGBUILD wrong in the file name.) You're fortunate that running The template I listed above contains lots of If you replace the package name with a hyphen, then There's mixed opinions on whether I think you're supposed to add
package() is manually copying the files. The template uses Fixing pkgver()I've been researching pkgver() for longer than I'd like, and How it works is that I'm planning to instead use Note that "commits since tag" is not monotonic and resets to 0 whenever a new tag is added. The wiki contradicts this by saying that Background: Pacman's version comparison algorithmThe output version comparison algorithm is that versions are split into segments, consisting of non-alphanumeric "filler" followed by either nothing but numbers or nothing but characters. (I have a longer article on Pacman's version comparison algorithm, but it's unpublished and unfinished, covers lots of edge cases and failure modes that real version numbers don't hit, and it's not easy to understand (IMO because the algorithm is confusing).) |
Thank you a lot for your efforts, it should now be available on the AUR. Feel free to close this issue if it works for you and looks ok, otherwise please let me know. |
Seems to work now, thanks for submitting! |
I want to install rgb_keyboard on Arch Linux without making difficult-to-reverse systemwide changes through
sudo make install
. I noticed that another of your repos (https://github.com/dokutan/mouse_m908) has a PKGBUILD. Is it possible to adapt it for this repo and publish it to the AUR?I'm currently building a PKGBUILD for rgb-keyboard-git to install the latest Git commit, unlike the mouse_m908 PKGBUILD which only installs a specific release. As a result, I'm researching
pkgver()
, and got lost documenting Arch's pkgver comparison algorithm (bad code consisting of layers of cruft and C string manipulation). Finishing this documentation will be slower than adapting a PKGBUILD directly (which I'm not motivated to do).The text was updated successfully, but these errors were encountered: