On Jun 12, 2009, at 20:08, Scott Haneda wrote:
I just hit the docs on port binary packages. More of an accident
but nonetheless, I am interested.
The full installer binaries that need not have macports installed,
are there more docs than the few paragraphs I've read so far?
Top of my list of questions:
Is this a reliable process, if so, why, with so many wanting a
solid php and apache has that not been done?
What archtecture is the build for? Only the build box, or are these
universal? If so, how is this being done with something like php
where I believe many modules simply can not build out as UB's?
It appears there is a single command. Does this create an installer
as well? Where are the usual install location selection, license,
and other features of installer creation defined?
Pretty excited to learn about this, looking forward to testing it out.
What documentation have you read?
I assume you're talking about the port pkg/mpkg/dmg/mdmg commands?
They package the port with exactly the variants you specify. If you
specify +universal, they're universal.
pkg creates an Apple Installer package of the port.
mpkg creates an installer package of the port and all dependencies.
dmg and mdmg do the same and then put the pkg on a disk image.
Binaries created this way aren't well supported, and certainly cannot
be mixed with an existing MacPorts installation in the same prefix.
_______________________________________________
macports-dev mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
