We'll skip the push-ups this time.
On Nov 6, 2008, at 00:17, Scott Haneda wrote:
Cool, thanks... Just skimmed the relevant parts of the guide. Will
read in detail as I go along. Strange, a little excited to get
started....
Thanks for everyone being so helpful, even on IRC, macports just
made my top 10 list of nice communities :) There are some rough
ones out there for sure.
Now watch someone jump my *** about top posting :)
On Nov 5, 2008, at 10:02 PM, Ryan Schmidt wrote:
Read the Guide. MacPorts executes many phases, such as fetch,
extract, patch, configure, build, destroot, install, activate, and
has default actions that it performs in each of those. These
default actions are sufficient for many kinds of software. For
example, the configure phase runs, basically, "./configure --
prefix=${prefix}" in the worksrcpath, and the build phase runs
"make". You can override bits of these phases as needed to adapt
to the particular software you're trying to write a portfile for.
_______________________________________________
macports-users mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
