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

source_changes at macosforge.org source_changes at macosforge.org
Tue Apr 3 17:02:15 PDT 2007


Revision: 23528
          http://trac.macosforge.org/projects/macports/changeset/23528
Author:   jberry at macports.org
Date:     2007-04-03 17:02:15 -0700 (Tue, 03 Apr 2007)

Log Message:
-----------
Add some thoughts on urls for network reachable ports and services.

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

Modified: users/jberry/mpwa/doc/design.txt
===================================================================
--- users/jberry/mpwa/doc/design.txt	2007-04-03 23:34:06 UTC (rev 23527)
+++ users/jberry/mpwa/doc/design.txt	2007-04-04 00:02:15 UTC (rev 23528)
@@ -122,11 +122,46 @@
 	  should be able to install any properly formatted port given a url to the port data package.
 	  (In other words, any url http://someurl that returns a properly formatted port package should
 	  be installable, whether or not it is hosted at macports).
-			
+	
+	- Should the actions below be added to the port command, or should an additional wrapper be
+	  created?
+	
+Potential public urls for ports:
+
+	A simple flat/short url to access and/or uniquely identify a port submission
+			(returns the portpackage for the submission)
+		http://port.macports.org/<submissionid>
+		
+	URLs to port page for a port:
+			(note that the <portname>.macports.org style might preclude use of hostnames
+			like rsync, cvs, etc. Or we could use macports.com or macports.net).
+		http://<portname>.macports.org/
+		http://www.macports.org/port/<portname>
+		
+	URLs to page for a port submission:
+		http://<portname>.macports.org/<submissionid>/
+		http://www.macports.org/port/<portname>/<submissionid>/
+		http://www.macports.org/submission/<submissionid>
+		
+	URLs to stable version of a port:
+			(redirects to the submission url for the appropriate submission of the port)
+		http://stable.macports.org/<portname>
+		http://port.macports.org/<portname>
+		http://port.macports.org/stable/<portname>
+		
+Issues for urls:
+
+	- do we have portnames starting with numbers or entirely composed of numbers?
+	- If a port is installed using a url that does a 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 submission that is desired, and yet maintain a one-to-one mapping between
+	  url and port.
+		
 ======
 
 			
-Actions:
+Potential port(1) Actions:
 
 	port submit
 			==> category

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


More information about the macports-changes mailing list