Technology

60102 readers

2726 users here now

This is a most excellent place for technology news and articles.

Our Rules

Follow the lemmy.world rules.
Only tech related content.
Be excellent to each another!
Mod approved content bots can post up to 10 articles per day.
Threads asking for personal tech support may be deleted.
Politics threads may be removed.
No memes allowed as posts, OK to post as comments.
Only approved bots from the list below, to ask if your bot can be added please contact us.
Check for duplicates before posting, duplicates may be removed

Approved Bots

founded 2 years ago

MODERATORS

[email protected]

882

Arch Linux and Valve Collaboration (lists.archlinux.org)

submitted 3 months ago by [email protected] to c/[email protected]

211 comments fedilink hide all child comments

We are excited to announce that Arch Linux is entering into a direct collaboration with Valve. Valve is generously providing backing for two critical projects that will have a huge impact on our distribution: a build service infrastructure and a secure signing enclave. By supporting work on a freelance basis for these topics, Valve enables us to work on them without being limited solely by the free time of our volunteers.

This opportunity allows us to address some of the biggest outstanding challenges we have been facing for a while. The collaboration will speed-up the progress that would otherwise take much longer for us to achieve, and will ultimately unblock us from finally pursuing some of our planned endeavors. We are incredibly grateful for Valve to make this possible and for their explicit commitment to help and support Arch Linux.

These projects will follow our usual development and consensus-building workflows. [RFCs] will be created for any wide-ranging changes. Discussions on this mailing list as well as issue, milestone and epic planning in our GitLab will provide transparency and insight into the work. We believe this collaboration will greatly benefit Arch Linux, and are looking forward to share further development on this mailing list as work progresses.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 1 points 3 months ago (1 children)

While I agree with the politics part (especially the notorious suspend-then-hibernate thing), I do see why a lot of devs would ask for systemd-init: to just bundle 1 kind of service instead of a gazillion. Same thing with Flatpak and not needing to build a gazillion binaries for every distro that hasn't packaged you, even though FLatpak's sandboxing away from native libraries is something I just don't like.

[–] [email protected] 1 points 3 months ago

I do see why a lot of devs would ask for systemd-init: to just bundle 1 kind of service instead of a gazillion

How would that work? There were N init systems with one "main" one, now there are N+1 init systems with one "main" one, just different.

Anyway, init systems for developers being problematic seem for me a nonexistent problem. Writing a systemd unit takes less time than writing this comment with tea and buckwheat with milk as a distraction. Writing a sysvinit script takes something like that too. Same with BSD inits. Same with openrc.

While combined they take some time, packagers can do that. And even if they can't, time spent trying to persuade others that systemd makes things easier is orders of magnitude bigger than time spent writing service scripts\templates\units.