2007/7/5, Anshuman Aggarwal <[EMAIL PROTECTED]>: > Yeah, that's what I had done as a workaround...I think the post install > script for the LibRSVG should do it...instead of generating a > conflicting file....or atleast it should instruct the user....but these > 'global' config files need to be maintained...but I bet that's what the > dev mailing list has been hot about for the last few weeks :)
There are a way to fix this by adding code to Compile/InstallPackage/SymlinkProgram to run these functions if some file exists. Much like I did for update-mime-database. Another approach is to add an API to the tools to be called from hooks in Recipes/PostInstall, e.g. Update_MIME_Database(), so the contributer/packager are responsible for calling the functions, if needed. First is better because it's completly automated, so the contributer wouldn't have to remember to call the function if needed. But fully automated *may* be errorprone. -- /Jonas PS this is the solution for the gconf problem as well - add a function that updates the global gconf file. _______________________________________________ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
