[23679] users/jberry/mpwa/doc/design.txt

[source_changes at macosforge.org]

Revision: 23679
          http://trac.macosforge.org/projects/macports/changeset/23679
Author:   jberry at macports.org
Date:     2007-04-06 12:14:13 -0700 (Fri, 06 Apr 2007)

Log Message:
-----------
Minor tweaks to mpwa design doc

Modified Paths:
--------------
    users/jberry/mpwa/doc/design.txt

Modified: users/jberry/mpwa/doc/design.txt
===================================================================
--- users/jberry/mpwa/doc/design.txt	2007-04-06 19:13:58 UTC (rev 23678)
+++ users/jberry/mpwa/doc/design.txt	2007-04-06 19:14:13 UTC (rev 23679)
@@ -77,7 +77,7 @@
 	 	the bundled set of the files that this requires: Portfile + /files
 		and any other relevant metadata or contents of the port directory.
 
-	- "pkgid": The unique id assigned to the submission of port portpkg at db.macports.org.
+	- "pkgid": The unique id assigned to the submission of a portpkg at db.macports.org.
 		
 	- "pkgurl": a url that uniquely references a portpkg.
 		This is probably formed in part from the pkgid.
@@ -115,8 +115,8 @@
 	  port information for local use by the user, though we might be able to live
 	  only with over-the-wire queries of the database. In any event, certain decisions
 	  made here will effect the local repository design:
-		- The pkgurl as a unique port descriptor
-		- n submissions/portpkgs of each port (even including potentially multiple 
+		- The pkgurl as a unique portpkg descriptor
+		- n portpkgs for each port (even including potentially multiple 
 		  portpkgs per epoch-version-revision)
 		- tags
 		- flags
@@ -163,7 +163,7 @@
 	- If a port is installed using a url that does a 301 (permanent) redirect to another port,
 	  the url remembered as the installed port should be the redirected target, rather than
 	  the original. This would allow the url for a stable version of a port to redirect to the
-	  particular instance that is desired, and yet maintain a one-to-one mapping between
+	  particular portpkg to which it resolves, and yet maintain a one-to-one mapping between
 	  url and port.
 		
 ======
@@ -197,7 +197,7 @@
 			<== reports (??? tbd ...urls to the reports? or text?)
 		-- Query reports for a given port submission
 		
-	port get (fetch conflicts with existing action!)
+	port get
 			==> pkgurl
 			<== portpkg
 		-- Bring a given portpkg into the local collection (or cache?) or portpkgs	

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.macosforge.org/pipermail/macports-changes/attachments/20070406/f71299bd/attachment.html