On Tue, Jun 10, 2008 at 5:34 PM, Carlo Calica <[EMAIL PROTECTED]> wrote: > On Tue, Jun 10, 2008 at 12:25 PM, mpb <[EMAIL PROTECTED]> wrote: >> 3) Whenever I upgrade Compile (via InstallPackage Compile) I am told >> that there is a new Compile.conf file, and asked which version I want >> to use. This is always a hassle, as I am never sure whether to use >> the new one (which will forget my compileRecipeAuthor setting), or to >> auto-merge (I don't trust automerges - perhaps I should) or to >> manually edit the files (which is work). >> >> Perhaps Compile.conf could, as a final action, source a >> CompileLocal.conf file? I could then put my settings in >> CompileLocal.conf, and then I could always use the new Compile.conf >> file. >> > > I use this technique for BootScripts (ie Bootup.local sourced from > Bootup) Any thoughts about carrying this over to other places it > makes sense?
Also: for conf files, a local conf file in ~/Settings/Scripts takes precedence over the one in /System/Settings/Scripts. (It (currently) does not read both, though.) -- Hisham _______________________________________________ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
