On 5/17/06, Lucas C. Villa Real <[EMAIL PROTECTED]> wrote:
Talking about dependencies, I'm dealing with situations here where they differ depending on the architecture being compiled. After all, we usually don't want tons of extra features on packages for the embedded.
I understand why but wouldn't it be confusing?
What about *Dependencies-$ARCH? That way we can have BuildDependencies-x86, BuildDependencies-ARM, BuildDependencies-MIPS and so on. If no "-$ARCH" file exists, then the existing ones are used for all architectures.
Hmm, $ARCH/Resources/*Dependencies is probably better. Is there any case where $ARCH/Recipe shouldn't override the base ./Recipe (or other files)? -- Carlo J. Calica _______________________________________________ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
