Carbon TODO

johnraff · 2025-09-28 23:42:41

This is a place to drop things that should be fixed before the Carbon official release.
Feel free to post - devs still reserve the right to ignore suggestions they don't agree with!

johnraff · 2025-09-28 23:49:33

BLOB needs going over so users who like the Boron (or other) look will easily be able to go back to it.

N.B. BLOB isn't a kind of system snapshot - it only preserves the appearance of other setups. This means, for example, there's no need to have a mechanism to restore tint2 for older looks - it's enough if we ship configs for xfce4-panel to look like the Boron (or whatever) tint2 panel.

But that means creating xfce4-panel config files for all the BLOB presets we plan to ship with Carbon. I think that's still easier than putting in things like prompts to install tint2? Or not?

Maybe long-term it would be simpler to have only xfce4-panel configs? (I think tint2 is on the way out anyway.)

Last edited by johnraff (Yesterday 00:02:18)

johnraff · 2025-09-28 23:58:02

Put the repo signing key in /usr/share/keyrings and add a "signed-by" entry to our sources list so apt will use it.

EDIT: upgraded bunsen-archive-keyring now uploaded. It puts a .pgp keyring in /usr/share/keyrings, and continues to drop an .asc in /etc/apt/trusted.gpg.d. I think we should make an announcement that the /etc/apt/trusted.gpg.d file will go away with Nitrogen, so people should make sure they add the "signed-by" entry by then. For iso installs we can handle it, but users upgrading from an earlier release will have to do it themselves.

And also (related issue) decide if we're going to ship deb822 sources or stay with the old version for another release.

Or maybe add a page to bl-welcome so the conversion can be done post-install.

Last edited by johnraff (Today 02:49:12)

johnraff · Today 06:17:18

packages, dependencies and upgrades

Our package bunsen-themes isn't actually used in Carbon, which gets its themes from bunsen-yaru-gtk

Up till now themes were organized like this:
bunsen-themes-base: contains only the theme(s) needed for the default desktop
bunsen-themes: contains the theme files used in the previous release, along with a few other popular ones
bunsen-themes-extra: more themes...

So, how about making the carbon bunsen-themes-base empty, but making it Depend on bunsen-yaru-gtk?
The advantage for users is that upgrades should go a bit more smoothly. They'll already have bunsen-themes-base installed and when upgrading to Carbon it will pull in bunsen-yaru-gtk.

(We can move the Boron theme files to bunsen-themes, and possibly a couple of less used themes from bunsen-themes to bunsen-themes extra.)

I don't think that's too controversial?

There's an advantage for developers too, that when there's a new BL release they don't have to update the theme package in the three different package lists we maintain (live-build for the iso, bunsen-meta-all and bunsen-netinstall) - just changing the dependency in bunsen-themes-base is enough (or optionally putting the actual files back there).

---

Perhaps we could also create an empty bunsen-icons-base package too, that would depend on whatever icon theme is currently used? Again, smoother upgrades and less work for developers. (It could be named bunsen-icons, but the -base name leaves us free to add another bigger icon package later, if we want to.)

hhh · Today 12:48:54

^ I'm fine with this. Thumbs up.

#1 2025-09-28 23:42:41

Carbon TODO

#2 2025-09-28 23:49:33

Re: Carbon TODO

#3 2025-09-28 23:58:02

Re: Carbon TODO

#4 Today 06:17:18

Re: Carbon TODO

#5 Today 12:48:54

Re: Carbon TODO

Board footer