On 5/15/06, Hisham Muhammad <[EMAIL PROTECTED]> wrote:
Different kinds of information that could be written/extracted:* BuildDependencies: handwritten file, in recipe, listing what's needed to build ("GCC [3.0,)") * RuntimeDependencies: handwritten file, in recipe and package, listing what's needed to run a package ("GCC [3.0,4.0)", maybe (not a particularly good example)) * PackageBuildInformation: generated file, in package, saying what was used during build (equivalent to current Dependencies file -- for reference only as an aid to write the other files?)
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. 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. -- Lucas powered by /dev/dsp _______________________________________________ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
