On Mon, Oct 03, 2005 at 07:56:18AM +0200, Marc Espie wrote: > On Sun, Oct 02, 2005 at 07:03:48PM -0700, Jacob Meuser wrote: > > but that's probably a dangerous patch. some qt applications do > > use ~/.qt for storing user configuration files. > Of course it's a dangerous patch! that's not what I meant. No, it would mean > really tweaking the code, so that the .qt creation doesn't happen unless > there's really some file you need to store there... which is a tad bit more > interesting.
yes. > > might it not be better to just set $HOME to somewhere that is OK to > > write to? > > Well, to me, it's a bug in qt. I don't see how a toolkit has a business > mucking with prefs files if you just run uic3/moc3... I could see having a user config file for uic or moc, which I believe is what's going on there. what I don't understand, is why it tries to create the directory in the QSettingsPrivate constructor, instead of when the files are actually accessed. I guess that's the point you made above. but then of course, qt programs probably rely on this behaviour and don't try to create ~/.qt themselves. I'll look into this a little more. the patch probably isn't so dangerous if combined with a patch that adds the directory, if it doesn't exist, when configuration files are created. I remember something about this from previous qt hacking, but the details are fuzzy ATM. -- <[EMAIL PROTECTED]>
