On 12/6/06, Jonas Karlsson <[EMAIL PROTECTED]> wrote: [...] > All suggestions require a new approach to meta recipes where sub > applications know of what main application they belong, so they can be > compiled and installed separatly. > All suggestions above also makes it possible to list sub apps as > dependencies, instead of having to install the complete meta recipe. > 3) and 4) is basicly the same but in 4) you don't have a file listing and > you dont care to remove old files from old sub apps. > 1), 2) and 3) makes it possible to create sub packages.
I don't like 3 at all, because it reminds me of the bad old days when I had to rely on a package manager's lists to know who put what files where (within a meta-recipe's program dir). It's still better than the current system where I have *no* way to tell that, but I prefer 1, 2, or 4 instead. My only meta-recipe issue is easy installation when one component fails to compile. When installing Xorg 7.0, about 5 (optional) pieces failed, and the only way I avoided wasting tons of time recompiling everything else up to that point was to edit the recipe and comment out each sub-package that I knew it had installed already, based on where it was in the list when it failed. With any decent sub-package system I could just skip (or comment out) the one piece I don't need, and answer "don't re-install" to the rest when it noticed I already had the same version installed. Any of your proposals would allow this functionality, so I'd like to see one of them added to Gobo. -Andy _______________________________________________ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
