[24525] branches/dp2mp-move/base/doc/INTERNALS
source_changes at macosforge.org
source_changes at macosforge.org
Fri Apr 27 08:28:29 PDT 2007
Revision: 24525
http://trac.macosforge.org/projects/macports/changeset/24525
Author: jmpp at macports.org
Date: 2007-04-27 08:28:29 -0700 (Fri, 27 Apr 2007)
Log Message:
-----------
Manually merging ryan's r24508 typo corrections to the INTERNALS file, along with other cleanups (Ryan, good for trunk? ;-)
Modified Paths:
--------------
branches/dp2mp-move/base/doc/INTERNALS
Modified: branches/dp2mp-move/base/doc/INTERNALS
===================================================================
--- branches/dp2mp-move/base/doc/INTERNALS 2007-04-27 13:37:20 UTC (rev 24524)
+++ branches/dp2mp-move/base/doc/INTERNALS 2007-04-27 15:28:29 UTC (rev 24525)
@@ -3,14 +3,14 @@
The MacPorts system is composed of a three TCL libraries:
macports - public API
port - portfile parsing and execution
- pextlib - neccesary C extensions to TCL
+ pextlib - necessary C extensions to TCL
- These three TCL libraries are grouped as a TCL "package". TCL packages
-allow for complex versioning and have a provide/require model of use, making
+ These three TCL libraries are grouped as TCL "packages". They allow
+for complex versioning and have a provide/require model of use, making
them well suited for maintaining a backwards compatable ports system.
- The "macports" TCL Library provides a public API into the mac
-ports system. Any external application wishing to manipulate a port can
+ The "macports" TCL Library provides a public API into the MacPorts
+system. Any external application wishing to manipulate a port can
load the "macports" TCL library. 'port', the included command line port
utility, uses only the exported "macports" API.
@@ -18,7 +18,7 @@
ports (ie, mportexec/mportopen/mportget). Also, the API has very little
knowledge of the contents of a portfile; instead, it relies entirely upon
the "port" TCL library. By keeping the high level API simple and generic,
-a revision of the underlying ports system will not neccesarily require
+a revision of the underlying ports system will not necessarily require
a revision of the high level "macports" API.
TCL packages allow for complex versioning with a strong requires/provides
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.macosforge.org/pipermail/macports-changes/attachments/20070427/5f424403/attachment.html
More information about the macports-changes
mailing list