On Fri, Mar 25, 2011 at 11:43, Mika Pflüger <deb...@mikapflueger.de> wrote: > Hi Tony, > > Am Thu, 24 Mar 2011 16:35:35 -0500 > schrieb Tony Gies <tony.g...@gmail.com>: >> 1. quasselcore.conf is not a user-editable configuration file and >> arguably isn't a configuration file at all. It stores basically some >> serialized objects representing the state of the core and changes >> frequently at runtime. > > Yes, you're right, I don't think quasselcore.conf is a configuration > file. We both agree that /var/cache is wrong, though. Additionally I > was thinking about quasselCert.pem, which definitively is a > configuration file and should be in /etc, at least I would expect it > in /etc.
Definitely arguable. Might be something to take up with upstream. > would have to think about a means of converting old installations of > quasselcore, I don't know how tricky this is, I guess we can write > appropriate postinstall et al scripts. I filed this same bug with the Ubuntu guys who had the same issue but appear to be tracking upstream directly rather than tracking unstable as I had previously believed; they moved everything to /var/lib in 0.7.2-0ubuntu1 and added a postinst script to deal with upgrading, which we could use as a reference. https://bugs.launchpad.net/ubuntu/+source/quassel/+bug/713462 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
