🏳️🌈 lesbian hacker in Berlin!
heavily involved in #LinuxMobile and @postmarketOS. Don't dm me for support, ping me in a public matrix channel.
I maintain U-Boot for Qualcomm devices and do other cool embedded stuff @ Linaro
"you are never beating the down bad allegations" ~ @isa
This account is mostly for technical topics, my personal account is @casey
| pronouns | she |
| GitHub | https://github.com/kcxt |
| Matrix | caleb:postmarketos.org |
| Website | https://connolly.tech |
really really considering hacking together some "smart mirror" so i can daily drive alpine edge and not worry about library updates making it impossible to install new packages on my system for days at a time
(no there hasn't been another breakage im just thinking about this a lot lately and kinda wanna do it for lols)
this would literally be some script and a hacked up version of pmbootstrap that figures out if there are any packages in any binary repo where other packages in any repo depend on conflicting versions and avoids updating them in the mirror.
This ofc would require a new signing key since you'd be rebuilding the APKINDEX
tbh at this point i just think it would be a fun technical problem to solve....
as a bonus it could be used to avoid updating dependencies (and everything that depends on them) where the postmarketOS forked version (e.g for systemd) hasn't been updated yet, which i still think is something we'll eventually in postmarketos if we want to be taken seriously. Even if we go fully immutable and ship binary deltas we still run the risk of breaking our image builders by not having something like this (or worse accidentally shipping the alpine version of a package....)
i don't doubt that Alpine will get a staging repo at some point hopefully in the not too distant future (something we might fund development for even) but that wouldn't solve the issue of our package forks being out of date
mkosi-sandbox is frickin AWESOME though, it's meant to be a CLI interface buuut I've vendored it and we're now using it as a library to unshare the entire process (rather than calling in to unshare each time we run a command) since this is how pmb worked before it's made the migration process easier.
it's basically like if bubblewrap was implemented in 1000 lines of Python, it's so nice and minimal
still not certain im on the right track but i think it's "good enough" in any case, comments from anyone knowledgeable about namespaces would be very welcome
https://gitlab.postmarketos.org/postmarketOS/pmbootstrap/-/merge_requests/2590
learnt so much about namespaces over the weekend for pmbootstrap i should really write a blog post or a thread or something about it some time
but ya this is like, the entrypoint to pmbootstrap now lol
@greenpeace hey, on your share page, after you sign, where is 'share on mastodon'?
Please fix. It should be at the top of the list, too.
🌈✨ vanta rainbow black ✨🌈
Computer Facts
-/mondstern
Greenpeace International
A Fine Day For Mischief 🏳️⚧️🏳️🌈🇺🇦🇵🇸
Viktor