If you're setting up patch repositories for a Linux distro, consider following a pattern like: current.my-distro.example <== current version10.my-distro.example <== current version9.my-distro.example <== prior Versus doing something like archives - when installing, use current. One of the issues with doing what Ubuntu does, for example, is that it breaks otherwise clean upgrade routes - because the URL's change when the software is archived. Using the version as a subdomain, you can just reassign the bugger to a new host without breaking the URL. You can, of course, do this at a proxy or load balancer also and Akamai or Cloudflare, for example, can route a /version9 or /version10 to a specific host. But it's fucking annoying to "/r/live-distro/arc-distro" when your distros already have fucking URL-valid unique identifiers. It's not that fucking hard not to require end users to open a fucking text editor on /etc to update your software. If you are hosting patches and your fucking patch infrastructure can't locate them because you shuffle URLs, then you're part of the fucking problem with Linux adoption. And if it's because you don't know how to configure nginx then you shouldn't fucking be involved with maintaining any Internet based patching system, full stop. Also if your software is fragile enough to work on just one distro, test for that distro in your install script and provide a container image for it - don't make users figure out errors. Also, if you use ./configure.s and ./Configure.sh, understand this is an issue over voice and readers? And the issue here is yes, yes, I've used Linux since it first showed up even though I prefer FreeBSD, OS/2 or even Windows still. I've used many distros, many real Unix, and even shit like GEOS and BeOS - even fucking CPM and Apple DOS/ProDos. And moreover, I've written software that had to run on all these things - and yes, I know "look for Configure vs. configure" - but if you look at your support mailing list, newsgroups or issues - take a look. How many users get it fucking wrong? If users cannot figure out how to do the thing, if they're pasting messages because they can't figure out how to get a tool they need to work - it's fucking annoying. And then in an organization, those complaints come to someone like me - some dino who pushes up their glasses and says... ah, yes... If Linux wants to displace Windows 11, it needs to push past the "you can build it from source" crowd. If you look at SteamOS, one of the reasons it's being more successful now is the SteamDeck has a pre-configured, optimized build that doesn't require "build and pray" - most users never see apt. If you look at Android, another popular distro, it's the same thing. Most people aren't accutely aware that it even is a Linux distro - they certainly aren't powering up bash or vi for administration of the devices or to join them to a corporate network. As Microsoft continues to cram AI down people's throats who don't want it, it's worth noting that people who are looking for an offramp need something that "just works." And there's a lot there that people in the community could do to help that experience, that maintainers can do to help it.