I don't know if GConf has some special considerations, but it seems like the best way to solve this problem is to symlink the files from their own Program dir into GConf's Program dir (or wherever they try to go). Then when you delete the program, all that's left behind is a broken symlink, which (I'm guessing) will be ignored properly. If not, then you just need to RemoveProgram it instead of deleting the program's folder directly, so that it can clean up the symlink it placed.
I modified my copy of the Gobo Scripts to do this (minus the RemoveProgram functionality), although I haven't ironed out all the bugs yet. I've also been using it occasionally as a hack if I can't get a program to respect any sort of $target directive and I don't want to take the time to make a patch, but that is of course very bad form and means I can't submit the recipes for those ones. I do plan to eventually (re)submit a cleaned-up version for possible inclusion in the mainline Scripts, because I think it is the best solution to those problems, but I need to be careful that it doesn't let me rely on it to correct badly-behaved programs, only ones that legitimately should have files in other programs' folders. Another solution would be to keep track of out-of-sandbox files in a special logfile in the Program's own dir, just to let RemoveProgram know it should clean them up, but this also destroys the ability to just delete the folder to uninstall. -Andy On 3/20/06, Hisham Muhammad <[EMAIL PROTECTED]> wrote: > On 3/9/06, Jonas Karlsson <[EMAIL PROTECTED]> wrote: > > I'm trying to create a recipe for gnome-vfs, but I'm stuck on the install > > script trying to install Gconf modules/settings in gconf settings > > directory. As it's gconftool that's used, I'm not sure what the operation > > is, if it's just about copying files or appending information to files. > > Anyhow, my suggestion is that the sandbox could be extended to some > > external directories, ie /Programs/Gconf/Settings, that you can specify in > > the recipe. This would also take care of the "problem" with kernel modules > > and the likes. > > Actually, you can do this now, but it's not pretty (in both senses): > > sandbox_options=( > --add-allowed /dir/foo:/dir/bar > ) > > The problem with this of course is that when you uninstall packages, > garbage is left behind, but I'm afraid that in Gconf's case there > might be no way around this. :( > > -- Hisham
_______________________________________________ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
