On Tue, 2004-06-22 at 14:43, Mark McLoughlin wrote: > Hi Joe, > > On Tue, 2004-06-22 at 18:29, Joe Marcus Clarke wrote: > > > This will affect us, as right now, no %gconf-tree.xml files are > > created. Therefore, we will have to go back through all of our ports > > that use GConf, and change the plists once gconf-2.7.2 (or whatever the > > release will be) comes up :-(. > > Okay, something here sounds wrong to my (probably tainted by RPM) ears > :-) > > Do plists contain the list of files in the package itself or the list > of files created by the progress of installing the package or both? Usually these two are one in the same. However, gconf changes this a bit. > > More importantly, can two packages have the same file in their plists? Technically, no. In fact, we've run into problems with gconf in the past where gconf keys are "owned" by different components. Mainly we live and learn, and fix problems as we encounter them. > > Because, if the answer to the latter question is no, then I don't think > these files should be in plists at all. What if two packages own keys in > the same directory? This is even more likely to cause problems now that > we're merging big sections of the tree into single files. Exactly. I was thinking of removing %gconf.xml files from plists, but there would be a lot of work involved. The one advantage of the way we have it now is that we are able to quickly spot problems when Makefiles get munged, and gconf schemas are not correctly processed. However, given this change, we may have no choice but to yank keys, and do scrollkeeper-like registration and deregistration. > > e.g. would you have the files in /var/lib/scrollkeeper in a plist?[1] No, these are generated during package installation. Joe > > Cheers, > Mark. > > [1] - Before somebody shouts at me that this implies that everything in > /etc/gconf/gconf.xml.defaults belongs in /var then yes, perhaps it does, > but I've no real firm opinion on that. If somebody does have firm > opinions on this, they belong on ongoing thread on gconf-list. -- Joe Marcus Clarke FreeBSD GNOME Team :: gnome FreeBSD org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome
Attachment:
signature.asc
Description: This is a digitally signed message part