#archlinux-ports | Logs for 2026-03-02

Back
[02:07:36] -!- drathir_tor has quit [Remote host closed the connection]
[02:08:03] -!- drathir_tor has joined #archlinux-ports
[04:13:23] -!- yjun123 has quit [Quit: Konversation terminated!]
[04:41:55] -!- marmis has quit [Quit: Bye!]
[04:42:38] -!- hcmb_ has joined #archlinux-ports
[04:42:38] hcmb is now known as Guest9998
[04:42:38] -!- Guest9998 has quit [Killed (calcium.libera.chat (Nickname regained by services))]
[04:42:38] hcmb_ is now known as hcmb
[04:43:22] -!- marmis has joined #archlinux-ports
[05:32:11] -!- yjun123 has joined #archlinux-ports
[05:32:16] -!- yjun123 has quit [Client Quit]
[06:17:06] -!- rafael_bento has joined #archlinux-ports
[06:45:54] <solskogen|M> greyltc: Without any kernel, IIRC.
[07:54:51] <yuvadm> is anyone working on an aarch64 RFC? is there a draft to contribute to?
[07:55:34] <solskogen|M> It is my understanding that, that is something that only the devs can do.
[07:56:21] <yuvadm> formally that makes sense I guess
[07:57:23] <yuvadm> but seems there's also non trivial work done by non-devs so i'm wondering how the knowledge should trickle upstream
[07:58:03] <yuvadm> (this also might just be an open topic, which is fair)
[08:42:50] <jelle> yuvadm: what do you expect of an aarch64 RFC?
[09:42:38] <yuvadm> jelle: specify how we support aarch64 both from the infra side of things (naturally more dev driven) and then also address how we do multi device support which is naturally more complex on arm (kernels, dtbs, bootloaders, etc.)
[10:10:11] -!- ektor5 has quit [Quit: WeeChat 4.3.4]
[10:22:09] -!- drathir_tor has quit [Remote host closed the connection]
[10:22:35] -!- drathir_tor has joined #archlinux-ports
[14:32:23] -!- yjun123 has joined #archlinux-ports
[15:08:06] -!- yjun123 has quit [Ping timeout: 246 seconds]
[18:01:00] <bschnei> yuvadm: the former seems to be an architecture agnostic subject and touched on in the existing Ports RFC. The latter could benefit from more open discussion pre-RFC IMHO and there is a spot that can serve that purpose already: https://gitlab.archlinux.org in other words, the lack of an RFC doesn't currently present any real obstacles
[18:01:00] <bschnei> to progress IMHO. also thanks for the MR!
[18:01:00] <phrik> Title: Sign in · GitLab (at gitlab.archlinux.org)
[19:11:57] <yuvadm> bschnei: thx for the pointer, good place to discuss i agree
[19:12:27] <yuvadm> and let me know if you need anything to merge it
[19:56:55] -!- gehidore has quit [Quit: brb parkour]
[19:57:48] -!- gehidore has joined #archlinux-ports
[20:21:59] -!- gehidore has quit [Ping timeout: 245 seconds]
[21:07:34] -!- gehidore has joined #archlinux-ports
[21:15:29] -!- gehidore has quit [Quit: brb parkour]
[21:16:27] -!- gehidore has joined #archlinux-ports
[23:10:12] -!- titus_livius has joined #archlinux-ports