!UUYziobKGGxpovWyAN:nixos.org

Robotnix

250 Members
Build Android (AOSP) using Nix | https://github.com/nix-community/robotnix77 Servers

Load older messages


SenderMessageTime
15 Jun 2026
@truelle_trash_queen:matrix.orgTheodora changed their profile picture.14:48:41
17 Jun 2026
@braid:alsace.hair@braid:alsace.hair joined the room.22:24:56
@braid:alsace.hair@braid:alsace.hair set their display name to The one with the braid (she/her) ⚡.22:25:33
18 Jun 2026
@cyclopentane:aidoskyneen.eupentane banned @braid:alsace.hair@braid:alsace.hair.06:27:02
@cyclopentane:aidoskyneen.eupentanesorry btw for not spending any time on robotnix in the past couple weeks, i've been unhealthily overworked from my full time job06:28:54
@cyclopentane:aidoskyneen.eupentane autra: I think your PR looks like the right way to go as a hotfix. However I tbh think that we should take this as an opportunity to completely rewrite repo2nin 06:30:26
@cyclopentane:aidoskyneen.eupentane * autra: I think your PR looks like the right way to go as a hotfix. However I tbh think that we should take this as an opportunity to completely rewrite repo2nix 06:30:27
@cyclopentane:aidoskyneen.eupentanei'm not happy at all with the spaghetti-esque state the code is in right now06:32:33
@cyclopentane:aidoskyneen.eupentanein particular, what needs to change is the git-repo manifest parsing. I'm currently modelling the manifest XML files essentially as key-value pairs of "relative path in source tree" => "git commit of source repository", but the way upstream git-repo operates makes them closer to "scripts" that are read from the top to the bottom06:34:42
@cyclopentane:aidoskyneen.eupentane for instance, there's a "command" called <remove-project> which removes a project that was defined further up, which is for instance used by the Waydroid manifest snippets: https://github.com/waydroid/android_vendor_waydroid/blob/lineage-20/manifest_scripts/manifests-33/01-removes.xml 06:35:45
@cyclopentane:aidoskyneen.eupentaneand yeah, if we want to sensibly support waydroid instead of hacking something together, repo2nix needs to know that "command"06:36:26
@cyclopentane:aidoskyneen.eupentanealso, on top of that, the current repo2nix architecture assumes that the update process is a straightforward "fetch manifest" -> "fetch lineage dependencies" -> "fetch git-repo dependencies" chain. With the addition of that new roomservice.py feature, a lineage-style dependency can now suddenly cause a manifest snippet to be parsed06:46:37
@cyclopentane:aidoskyneen.eupentanethe way my updating architecture does toposorting of dependency fetching graphs already is a big mess, and what we'd need is a unified way for the fetching process to generate the fetching graph on-the-fly. would also help for parallelism.06:48:15
@autra:trancart.euautrano problem, you owe us nothing. Thanks for spending so much time on it! 08:55:36
@autra:trancart.euautra do you mean that order is significant? If remove-project happens before (on the order of reading) a project is added, will it remove that project or not? 08:57:07
@autra:trancart.euautrawhich roomservice.py are you referring? I've only found https://github.com/Lineage-OS/android_vendor_cm/blob/177ab036d0486e60b8d8000258069bed5dfc18e9/build/tools/roomservice.py, which seems to be very old.09:00:54
@cyclopentane:aidoskyneen.eupentaneYes exactly09:01:37
@autra:trancart.euautraomg but why? 😆09:02:05
@cyclopentane:aidoskyneen.eupentanethe one in android_vendor_lineage09:02:10
@cyclopentane:aidoskyneen.eupentaneBecause git-repo is fucking garbage, simple as :D09:02:23
@cyclopentane:aidoskyneen.eupentanethat's why LineageOS had to design a suite of hacky Python scripts around it to get any serious work done at all09:02:50
@autra:trancart.euautraYou'd think google would spend enough resources on a tool that is so used in their workflow.... :-/ 09:03:39
@autra:trancart.euautraOk, I've searched in lineage-os github org, which is NOT the same as LineageOs org09:04:17
@cyclopentane:aidoskyneen.eupentaneyeah, but unfortunately i think that more often than not, "it works well enough" is a killer argument for never doing anything against tech debt in corporate environments09:04:55
@cyclopentane:aidoskyneen.eupentanethe AOSP signing scripts are similar man made horrors beyond comprehension09:05:21
@cyclopentane:aidoskyneen.eupentanelike. literally every single custom ROM has some sort of bespoke mechanism for wrapping git-repo because it's so useless09:06:48
@cyclopentane:aidoskyneen.eupentaneIt's a failed experiment from the early days of git and was meant to provide for a generic way to do dependency management with git09:07:36
@cyclopentane:aidoskyneen.eupentane(hence the generic name)09:07:43
@magic_rb:matrix.redalder.orgmagic_rbMaybe it should join the killed by google fsmily then09:11:27
@piegames:flausch.socialpiegames joined the room.09:22:12

There are no newer messages yet.


Back to Room ListRoom Version: 6