On 15.12.2010 08:33, Yves-Alexis Perez wrote: > On mar., 2010-12-14 at 23:43 +0100, Michael Biebl wrote: >> I'm using a custom theme for plymouth and desktop-base overwrites that >> setting on each upgrade. > > The same is true for splashy and grub, was true in Lenny (and Etch, I > guess). I can't speak for splashy, but for grub the alternatives system is used, so my changes are preserved on upgrades. >> >> I'm filing this bug with severity serious as the package overwrites >> custom configuration in /etc/ (/etc/plymouth/plymouthd.conf). > > To be precise, no, it doesn't overwrite the configuration. But yes, it > sets the default theme (by calling the relevant plymouth command). > > The whole point of desktop-base is to provide a theme for the whole > desktop. For now, if you want to only use a subset of the themes, yes, > you have to reconfigure that at each upgrade. If you have an idea on how > to do that more smoothly, you're welcome to propose it. We could also use alternatives here. Say, plymouth ships with a default configuration that says Theme=debian-plymouth-theme (or so), which is an alternative that by default points to text. desktop-base could install the new theme as alternative with a higher priority. One neat thing of this approach would be (given we have different themes), that we could use slaves to switch all alternatives in one go to a new theme  Cheers, Michael  "It is often useful for a number of alternatives to be synchronised, so that they are changed as a group; for example, when several versions of the vi(1) editor are installed, the man page referenced by /usr/share/man/man1/vi.1 should correspond to the executable referenced by /usr/bin/vi . update-alternatives handles this by means of master and slave links; when the master is changed, any associated slaves are changed too. A master link and its associated slaves make up a link group" -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
Description: OpenPGP digital signature