[23538] users/jberry/mpwa/doc/design.txt
source_changes at macosforge.org
source_changes at macosforge.org
Tue Apr 3 18:58:33 PDT 2007
Revision: 23538
http://trac.macosforge.org/projects/macports/changeset/23538
Author: jberry at macports.org
Date: 2007-04-03 18:58:33 -0700 (Tue, 03 Apr 2007)
Log Message:
-----------
Yet more typos
Modified Paths:
--------------
users/jberry/mpwa/doc/design.txt
Modified: users/jberry/mpwa/doc/design.txt
===================================================================
--- users/jberry/mpwa/doc/design.txt 2007-04-04 01:53:59 UTC (rev 23537)
+++ users/jberry/mpwa/doc/design.txt 2007-04-04 01:58:33 UTC (rev 23538)
@@ -119,13 +119,13 @@
directory structure.
- What does it mean to flag a port as stable? Is there only one such designation per port?
- Once a submission is flagged as stable, does the previous such such stable port version
+ Once a submission is flagged as stable, does the previous such stable port version
lose that designation? Or is it possible to determine that a port submission was previously
stable? And if so, that brings up the need to be able to determine the "latest stable"
submission of a port?
- Though we provide a network-accessible location and unique urls for ports, we should not
- restrict the ability to install an http:scheme port to only this repository. The port command
+ restrict the ability to install an http:scheme port only from this repository. The port command
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).
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.macosforge.org/pipermail/macports-changes/attachments/20070403/7113c83d/attachment.html
More information about the macports-changes
mailing list