03:26 <tpw_rules> how does the project keep track of it?

09:00 <j`ey> tpw_rules: what do you mean?

10:00 <marcan> tpw_rules: https://src.fedoraproject.org/group/asahi-sig this is probably the easiest way to find all the upstream RPMs we're involved with

10:01 <marcan> but also now that the core m1n1/boot/initramfs type stuff is taken care of, there isn't much special sauce left packaging-wise really

10:01 <marcan> all the audio stuff is "just packages"

10:01 <marcan> the packaging is trivial, modulo distro/package manager specific details that would vary anyway

12:22 <jmr2> Not sure if that's what tpw_rules meant, but PKGBUILDS is my go-to place for kernel build options as well as figuring out which tags is the recommended one.

12:22 <jmr2> Example: whe speaker wiki page says to use 6.5-25 or newer. Which one among the newer should I use, and where do I find that info in the Fedora repos?

12:23 <j`ey> jmr2: I asked about this, and the issue is that fedora applies the patches to stable linux versions, they dont use the tags as is

12:24 <j`ey> (currently it's based on -24 + some extras?)

12:29 <jmr2> Saw that - it looks like a lot of cherry-picking. But that's why it'd be hard to use fedora as a reference tree.

12:31 <j`ey> yeah there needs to be a way for other distros to know what tag to use

15:36 <tpw_rules> exactly

15:36 <tpw_rules> but if the arch distro is slowing down, is PKGBUILDs still a good place?

17:17 <opticron> oooh, debian updates

17:44 <mps> alpine mostly follows latest tagged things