On 8/14/06, Hisham Muhammad <[EMAIL PROTECTED]> wrote:
I like this. My feeling about sorting out dependencies is that we can't rely on general schemes for handling version numbers, but each project defines their own conventions. What I like about your proposal is that (again, in my gut feeling) these per-project conventions can be mostly relied on. With your X.Y.Z scheme we could 'encode' these conventions in recipes and that could largely automate the conversion process, in a documented (and still overridable) way.
I like this too. One concern is the "GCC || LibStdC++" notation. It is possible to return true with LibStdC++ but the dependent is a C prog so the GCC is what really matters. Given the C ABI stability (versus C++) this may not be an issue. Also need a way to support projects that change ABI compat without a sensible version numbering. Maybe a sh function with a case in it?? -- Carlo J. Calica _______________________________________________ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
