On Tue, 2008-10-28 at 15:21 +0100, Yves-Alexis Perez wrote: > > > > Now, about splashy_config breaking when /etc/splashy/config.xml does not > > exist, this is the right thing to do because without that > > file /sbin/splashy won't work anyway. Why would somebody remove this > > file from /etc/splashy? Let's see what we can do about this one. > > Well, I agree that it should fail if it can't install theme. But in your > case, /etc/splashy is *not* reliable. It can't know if it's a link or a > folder. In your case, if you want to remove /etc/splashy, you should > directly use /usr/share/splasy/config.xml. And you should have moved > conffile from /etc/splashy to /usr/share/splashy and let the folder.
Ummm... What happens when users install their own custom themes and modify Splashy to use this new theme, then they install a new version of Splashy? Will their changes to config.xml be kept? I though /etc/ was supposed to be for configuration files that the local sysadmin (end-user) controls and no package should mess with these local modifications. Moving config.xml to /usr/share/splashy/config.xml will defeat this purpose and allow the file to be changed during upgrades. No? We have a few Debian developers on #splashy. Please join us. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
