I suppose if you want to be able to copy the rules directly without having to install as an RPM, the
I suppose if you want to be able to copy the rules directly without having to install as an RPM, then we could make further changes:
JThat way they can be consumed as an RPM or as plain files
JI need to do dad stuff for a bit but will be back in a bit to wrap it up
CHow do I conveniently install command line utilities like fzf, xclip, xsel, and calc without layering them?
Bwell i guess all there is to do is copy the rpm use rpm-ostree to install and remove the rpm that should be it right
BBthis kind of a snippet
Jlet's figure out how to fix it in the repo so that we don't need to put that huge line in each containerfile?
Bwell currently what is happening is there is no /etc/udev/rules.d in the udev-rules image so it cant copy
Bso all you need is all udevrules in udev-rules image currently there is only the rpm
J@Bigpod ^^
Byea tthat should work, im currently using in my fork the approach i copied in
Bwith installing the package and removing rpm file afterwards
Bboth should work
MIf everyone is installing then deleting the RPM what’s the value of the RPM?
Bi most defenetly agree, that was just easiest way to get it working with resources at hand as while i was looking into it didnt know which way jorge wanted to go
Bill probably update my fork to reflect whichever way ublue does it
Jyeah I am standing by
Blet me know when you make the changes
J
Jok, this looks like it also means no one has to change their COPY lines, which is a double bonus
Jor just do the
--from /ublue-os-udev-rules right?JYeah
JThat way you don't even have to remove the *.rpm
JSo we end up with
COPY --from=ghcr.io/ublue-os/udev-rules /ublue-os-udev-rules/* /etc/udev/rules.dJYou can always run the RPM through cpio if you have a system that doesn't use rpm directly, but these changes skip that step for you
Jyes please, remember I am old, learning a new packaging system will break me
JI think more like
/ublue-os-udev-rules/usr/lib/udev/rules.d/*Joh goodness lol
BThis change looks good to me
J@Bigpod put the review in github so we can start practicing to do it
Jand then I'll add mine
Jand then update the readme
Bi dont have review permission
Jhuh, I set them all to have that on yesterday
Bmaybe some setting is wrong becuase it says reviewers with write access, and it also could be since i do not have any contributions anywhere in ublue-os org
Joh, good opportuntiy to test the docs, one sec!
JBahh yea been a while since i have done reviews in github or reviews at all
Jyeah, because I ran into this too
Jyou can review but you don't know it unless you start at the bottom link
JThis seems to be all you'd need to copy:
Joh, duh, of course
Jthat makes sense, just use the root
Jlol how obviously simple
Badded a approval review
JIt basically gives you
rpm -ivh -like powersJ@Bigpod I'll fix the docs as a PR, and then if you can review the 3 PRs that are left we'd be done with this bad boy
Jand then I'll post an update in the forum like how jstone did for the nvidia one
Jok, pushed, if you'd do the honors!
JI forgot to add the release-action to this repo
