ubuntu-rockchip NG

[briantopping]

I'm setting up a server install for OPi CM5 with eMMC that needs partitioning to isolate /var/{lib, log} from the rest of the system, along with full disk encryption and LVM. I see where to do that, but something crossed my mind as I approached the problem. My thought process is my needs for partitioning are going to be different than others and whether the solution should be generalized rather than creating a new conditional branch. This isn't scalable, so the changes don't get accepted in a PR and then I'm on a fork.

As I started to consider the autoinstall features of Subiquity, I recognized the need to restructure the scripts that currently exist in to a repository of package using preinst and postinst hooks for the tasks that the scripts currently do and pipelines to feed the packages.

I saw @Joshua-Riek's post here. Breaking the entire project down into a series of Debian builds for different board features is a great way to solve that issue. They can either fix the problem themselves or hire someone in the community to do it. It's really up to them at that point to pay up, who they pay is really up to them. This is cynically called "professional open source" and everyone does it one way or another.

Interested in whether this post sparks a discussion. I think it could be started very organically by picking a board and converting some small leaf components to packages, then working upwards.