I am still not understanding why this is a seperate repo, I thought you were just making a new image
I am still not understanding why this is a seperate repo, I thought you were just making a new image page that autogenerated the list of images?
JI believe this change should be an easy review https://github.com/ublue-os/nvidia/pull/50
GitHub
This change adds the steam-devices package which adds some udev rules for using Steam hardware. This package will be unneeded in the future when the rules are upstreamed:
systemd/systemd#22681
systemd/systemd#22681
Jdone, if you have time to take a look at the udev repo it worked awesome locally but doesn't build in github, I'm kind of at a loss to the why?
XI wasn't just making another page on MkDocs to;
- Seperate the custom code and drop-in docs website generator.
- Not have to learn an entirely new, mostly foreign system for generating these changes.
- Replace the list of artifacthub widgets with one totally under control, with custom branding and better UX for someone just looking to rebase to an image.
- Include advanced filtering, without making a mess with vanilla js and use the elegant reactivity of svelte.
Also, doing that wouldn't have been that fun for me personally.
XFifth reason–I think it's a shame when a cool project has a generic webpage. Even just having a custom frontpage with a link to whatever docs website generator instantly just feels better to me.
JHere's what I did
JAnd for the specfile
Jhah did you just rewrite the whole thing instead?
JI've been making a habit of stuffing add-ons like this into RPMs because then it integrates nicely into the RPM database and you can introspect with
rpm -ql $PACKAGEJI had a working example that just dumped the files into /usr/lib/udev/rules.d, but for the number of files being added it's sensible to have them all tracked, and rpm-ostree will quit early if you attempt to overwrite files during the build
Jdo you want to just PR this? I can close mine
JGitHub
A layer for adding udev rules. Contribute to ublue-os/udev-rules development by creating an account on GitHub.
JWe want them included as well?
Jyeah I figured we need a way to add the gaming ones
Jbut also other ones we might find
Jlike I need the titan key stuff for work, etc.
Jand there are for sure more I want to add
Jbut I didn't know someone was collating the gaming ones so that was really handy
Jlike I think there's yubikey ones and others we'll still need to go find
JAck
JGitHub
Provides library functionality for FIDO2, including communication with a device over USB or NFC. - libfido2/70-u2f.rules at main · Yubico/libfido2
Jbut I'll wait until you're done and then I'll PR this in so I can learn where to put it, etc.
Joooh, look what I found from the rpm-ostree repo: https://github.com/redhat-plumbers-in-action/differential-shellcheck
GitHub
GitHub Action for running ShellCheck differentially - GitHub - redhat-plumbers-in-action/differential-shellcheck: GitHub Action for running ShellCheck differentially
GitHub Action for running ShellCheck differentially - GitHub - redhat-plumbers-in-action/differential-shellcheck: GitHub Action for running ShellCheck differentially
Joh so I just leave the rules we want also in there in etc/udev/rules.d in the repo then?
JADD etc /tmp/ublue-os-udev-rules/etcJthat's what that does?
JYeah, the idea is that you may place as many custom udev rules as you'd like inside this repo, and add additional rules from other sources like with the game-devices-udev rules
Jack, ok I'll remove the now-duplicate steam rules
JThis is what the file contents look like https://gist.github.com/joshua-stone/81aae2cebcd2c0c9e1f521f8e1566180
CI mention something once and within 8 hours y'all have it not only upstreamed, but optimized and then generalized
JIt's a hobby
J
C
so it isJah nuts I merged instead of branched and PRed
Jshould we turn on branch protection in this one?
JProbably a good idea, yeah
Jhuh, what happened there
JYou have to make sure the files you remove are reflected in the specfile https://github.com/ublue-os/udev-rules/blob/main/ublue-os-udev-rules.spec#L31
GitHub
A layer for adding udev rules. Contribute to ublue-os/udev-rules development by creating an account on GitHub.
CWas silverblue-nvidia already in the works or partly started because of my recurring commentary on driver management and backup channels?
CI would assume the former but the timing seemed to be there for the latter
Jok so I think removing line 35 is what I need?
JI removed the license file since it came with the steam rules
JYeah, that sounds about right
J
JI think I had been telling you about the merits of SB for a while, but it looks like a month and a half ago was when @j0rge asked me if I wanted to do a prototype to show off the fairly new container-native support
Jok I just need 2 quick reviews and we're in business!
JJI had been following development but didn't have a compelling use case that would be immediately beneficial for my own PC, but giving me the idea to start a project for helping other people was the lightbulb going off in my head
JAaand we're passing
JGood work team
