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. > 2. The data directory is a build option and the database along with > quasselcore.conf is stored in that directory. To change this behavior > you would have to actually patch quasselcore. This is not, of course, > a definitive reason not to do it, but does complicate matters. I see how this complicates matters, but I think in order to actually be able to claim support for encryption, we must support easily changing the certificate for a proper one and as this is a local configuration option it should reside in /etc. Maybe a symlink in the quasselcore data directory pointing to the actual /etc/quasselcore/quasselCert.pem might solve the problem without patching. If we agree on quasselCert.pem being a configuration file and the others being "Variable state information" and thus belonging into /var/lib I could try to prepare patches to the packaging to change the locations. We 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. Cheers, Mika -- Own your own computer. Don't use Windows 7. <http://windows7sins.org>
signature.asc
Description: PGP signature
