• 0 Posts
  • 151 Comments
Joined 11 months ago
cake
Cake day: January 2nd, 2024

help-circle








  • It’s not quite what you’ve asked for here, but as a Dev I’d be remiss if I didn’t shill for Gentoo.

    It ticks your rolling release box, has fantastic docs, a huge package repository (and the community repo Guru), and by design enables almost infinite configurability and customisation. We also have a binary package repository now for popular architectures, so you can choose to avoid compiling if you don’t want to deviate from sane defaults (or only compile in cases where you do!)

    On the hardware side, we have fantastic support for a number of architectures, I recently brought up a SPARC system and have some arch64 and riscv in the past.

    Finally, even if you just decide to check the distro out, the process of installing, configuring, and maintaining a Linux system is outlined in detail within our handbook, and can provide a peek behind the scenes at what some other distros abstract; it’s a fantastic learning experience for those interested.

    Finally, we have fantastic support through volunteers in official IRC channels and forums, as well as unofficial hubs like discord.

    Hopefully I’ve planted a seed and you’ll check it out down the line. :)






  • I’m a huge proponent of Gentoo Linux as a learning experience. It’s a great way to learn how the components of a system work together and the distro enables an amazing amount of configurability for your system.

    Even following a handbook install in a VM can be a good experience if you’re interested.






  • You don’t have to!

    If a downstream distribution wants your software they will build and package it themselves and maintain that infrastructure.

    You could provide an example rpm spec (etc) to make their lives easier but it’s not on you to provide a binary package that works everywhere; you released the source code so any given user / distro can compile it for themselves.

    Just make sure that your build infrastructure and docs are up to speed, and ideally implement some CI/CD and testing to catch any breaking changes.