But are we planning to have different six-monthly and nightly distributions? Will that switching even happen? With a single repo, you can just hold back the kernel package and some other fundamentals (uutils and such) until it is time for a new "release".
Against that, maintaining a number of small repos is much, much easier than one enormous repo (I had a repository ten years ago, so I am speaking from experience here). If there is an error, it only affects a small number of packages. But that would equally apply to "RenkuPorts" We could consider the following:
- RenkuOS_core > equivalent to the "Haiku" repo - contains everything that will end up in the "release"
- RenkuOS_audio
- RenkuOS_business
- RenkuOS_development
- RenkuOS_education
- RenkuOS_fonts
- RenkuOS_games
- RenkuOS_graphics
etc etc. You'd probably have to throw in RenkuOS_libs and RenkuOS_misc
So even if the games repo goes offline for some reason, the others are still available. A single big repo is a single big point of failure.
FWIW I'm looking to set up something from my own ports collection. so far, I'm thinking of
- any > wallpapers and fonts
- cli > My soft spot, I know
- michel > My yab programs
- ports > A subset of my ports. Not five text editors, just one that really fills a gap. The other four can still be downloaded from my website.
Anyway, there are good arguments either way, but "That's how Haiku did it" can no longer be gospel for us. They decided on that arrangement in very specific circumstances, and they are stuck with it. Whatever we decide, we will be stuck with, so let's at least consider the possibilities.
