Platform versions and Binaries

Anders F Björklund afb at macports.org
Sun Jul 1 05:10:50 PDT 2007


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 archives, and ditto for FreeBSD STABLE and CURRENT...


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/
...

This goes for /opt/local/var/macports/packages, and for
remote fetching. It also goes for all RPM repositories.


Universal packages should probably go in a special place
too, since they use the 10.4.u SDK and the "fat" arch ?
Eventually one _might_ want to share "noarch"* packages
between architectures, and maybe even between platforms.

--anders

* http://trac.macports.org/projects/macports/ticket/12206




More information about the macports-dev mailing list