Juan Manuel Palacios wrote:
There is a upcoming problem that will occur with the binary
archives/packages, in that most of the code currently only
checks for ${os.platform} and ${os.arch} when looking for
binaries, ignoring ${os.version} which might be important ?
When you say this, what exac
Rereading this initial post after Kevin committed r26693, with which
we're now recording ${os.major}.
On Jul 1, 2007, at 8:10 AM, Anders F Björklund wrote:
There is a upcoming problem that will occur with the binary
archives/packages, in that most of the code currently only
checks for ${o
So we might need to include at least the major version in
the paths used, so that they will become something like:
darwin/9/i386/
darwin/9/ppc/
darwin/8/i386/
darwin/8/ppc/
darwin/7/ppc/
freebsd/7/i386/
freebsd/6/i386/
freebsd/5/i386/
...
There is now an ${os.major} variable that can be used fo
There is a upcoming problem that will occur with the binary
archives/packages, in that most of the code currently only
checks for ${os.platform} and ${os.arch} when looking for
binaries, ignoring ${os.version} which might be important ?
e.g. Panther and Tiger will try to use the same binaries
and
