[25179] users/jberry/mpwa/doc

[source_changes at macosforge.org]

Revision: 25179
          http://trac.macosforge.org/projects/macports/changeset/25179
Author:   jberry at macports.org
Date:     2007-05-15 09:13:03 -0700 (Tue, 15 May 2007)

Log Message:
-----------
mpwa: a bit of documentation cleanup

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

Modified: users/jberry/mpwa/doc/design.txt
===================================================================
--- users/jberry/mpwa/doc/design.txt	2007-05-15 15:48:17 UTC (rev 25178)
+++ users/jberry/mpwa/doc/design.txt	2007-05-15 16:13:03 UTC (rev 25179)
@@ -78,35 +78,8 @@
 	- "pkgurl": a url that uniquely references a portpkg.
 		This is probably formed in part from the pkgid.
 		
-Storage layout within the macports subversion repository:
-
-	/portpkgs
-		/common (revisioned/shared between instances of a port)
-			/first-letter-of-portname
-				/portname/<directory tree> (the unbundled/uncompressed portpkg)
-		/low-6-bits-pkgid-2char-hex
-			/next-6-bits-pkgid-2char-hex
-				/pkgid-zero-padded-dec
-					/portpkg.tgz (the bundled/compressed portpkg)
-					/unpacked/<directory tree> (the unbundled/uncompressed portpkg)
-					/meta
-						/submission_info
-						/comments (user comments?)
-						/reports (build logs?)
-						/status (build status?)
-					/binaries (potential future expansion)
-			
 Issues:
 
-	- It is not determined yet to what degree port meta information should be stored
-	  in the database vs in the portpkg directory. It's likely that much such
-	  metadata (flags, tags, version, etc) should be at least shadowed into the
-	  database. Some port information (such as comments or build reports) might
-	  live well only in the directory, and not in the database.
-	
-	- The package/archive format to use for ports is not yet determined (though .tgz
-	  is used currently). xar is a likely a good choice, though it will mean more work on tiger.
-	
 	- We may need a means to build and/or fetch a local repository of the
 	  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

Modified: users/jberry/mpwa/doc/portpkg-design.txt
===================================================================
--- users/jberry/mpwa/doc/portpkg-design.txt	2007-05-15 15:48:17 UTC (rev 25178)
+++ users/jberry/mpwa/doc/portpkg-design.txt	2007-05-15 16:13:03 UTC (rev 25179)
@@ -11,12 +11,14 @@
 
 	- <portname>.portpkg
 	- file extension: .portpkg
-	- mime-type: application/macports-portpkg
+	- mime-type: application/vnd.macports.portpkg
 	
 The naming of a portpkg using the portname is not guaranteed in all cases, but it
 a suggestion. And in particular, certain characters in portnames may be omitted or
 changed to ensure valid and simple file names.
 
+The mime-type application/vnd.macports.portpkg has been registered with the IETF.
+
 portpkg files
 =============
 Files in a portpkg are mostly just the contents of the port directory, rooted at portpkg:

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