62
Void Linux maintainer orphans 100+ packages over AI policy dispute
(www.phoronix.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 12 Sep 2026
62 points (98.4% liked)
Linux
19060 readers
477 users here now
Welcome to c/linux!
Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!
Rules:
-
Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.
-
Be respectful: Treat fellow community members with respect and courtesy.
-
Quality over quantity: Share informative and thought-provoking content.
-
No spam or self-promotion: Avoid excessive self-promotion or spamming.
-
No NSFW adult content
-
Follow general lemmy guidelines.
founded 3 years ago
MODERATORS
There might be a bit confusion. A package maintainer does not (necessarily) author the packages (the source code of the projects they contain), but typically maintains build scripts and security patches for upstream packages maintained by their authors. This is necessary because build systems and scripts are complex and packages from one distro would usually not fit into another one.
In other words, most code he/she produces are build scripts, and testing and adapting updates. And yes, this is still a lot of work.