A dev progress update on ubuntu desktop provisioning

Desktop
, , ,
7

@eeickmeyer:

I mean, I’m all for the fallacy of sunk cost, but does this mean that we’re no longer depending on the ubuntu-flavor-installer framework in the very, very near future? This means that all the work we’ve all just done is all-for-not and it would’ve been nice to know this ahead of time. I guess either way this got us ready for what’s coming, so there’s the silver lining.

The ubuntu-flavour-installer uses ubuntu-desktop-provision as a git submodule. So, if you’ve made ubuntu-flavour-installer work, and provided you haven’t customised massively, then it should be straightforward to migrate.

@eeickmeyer:

Looking at whitelabel.yaml, it looks fairly incomplete in terms of documentation as to what can be done with it.

As I mentioned above, the format should come out later this week and we’re open to comments to make sure it meets flavour requirements. However, for this iteration we didn’t plan on supporting custom layouts due to resource constraints. With regard to asset location but the working assumption is that will look something like this:

/usr/share/desktop-provision/
  /assets/
  /slides/
  /eula/ # oem only
  - whitelabel.yaml

@eeickmeyer:

Can you provide some context? What is this?

I assume you’re referring to ubuntu-desktop-init, if so, this is essentially a replacement for gnome-initial-setup and our support for an OEM/OOBE. Read about Stages 4 and 5 here .

With regard to using your flavours accent colours, we expect that to be set in whitelabel.yaml. I was specifically referring to the screen in the installer where the end user could set a dark/light theme and accent color for the default desktop.

Hope that helps!

1 Like