Changes between Version 2 and Version 3 of SummerOfCode2014_interactive

Timestamp:

Jun 24, 2014, 2:46:21 PM (10 years ago)

Author:

shasha@…

Comment:

--

SummerOfCode2014_interactive

@@ -51 +51 @@
 
 
-=== Apt-get like behaviour ===
-Desc: When installing a port, list all the dependencies and ask the user for confirmation just like apt-get does.
-
-Message: A list of all the dependencies.
-
-Question type: A continue/abort question to give the options of continuing with the installation or aborting it. This could even use a 10s timeout, giving an option to abort during the timeout and continuing automatically after the time is out.
-
-Example-
-{{{
-$> port install foobar
-The following dependencies of foobar will be installed:
-  boofar @0.0.1 +xzy
-  barfoo @0.0.2 +xzy
-  foba @0.1
-Continue? [Y/n]: Y
----> Installing boofar @0.0.1 +xzy
----> Installing barfoo @0.0.2 +xzy
----> Installing foba @0.1
----> Installing foobar
-$>
-}}}
-
 === Dependents getting broken ===
 Desc: When uninstalling a port, if ports that depend on it are getting broken
@@ -93 +71 @@
 }}}
 
-=== Variant specific dependency ===
-Desc: When installing a port that requires a dependency to have a certain variant, but this variant is not set. Ask the user if it should reinstall the dependency with that variant. This interaction is currently marked low priority.
-
-Message: A warning message explaining that reinstalling with a specific variant could break any already-installed dependents that relied on the previously-selected variants.
-
-Question type: A yes/no question is suitable here. The correct variant will be selected and installed automatically so no need to provide options. 
-
-Example-
-{{{
-$> port install foobar
-The package 'foobar +quartz' requires 'barfoo +quartz' but 'barfoo' is installed.
-Warning: Reinstalling with a specific variant could break any already-installed dependents that relied on the previously-selected variants.
-Do you wish to install barfoo +quartz? [Y/n]: Y
----> Installing barfoo @1.0.1 +xzy
-——-> Installing foobar
-$>
-}}}
 
 === Ambiguous activate ===
@@ -127 +88 @@
 Type a number to select the variant to activate: 2
 ---> foobar @0.0.2 +xzy activated.
-$>
-}}}
-
-=== Rebuilding in rev-upgrade ===
-Desc: Before rebuilding any port in rev-upgrade the user will be asked for confirmation.
-
-Message: A list of ports that will be rebuilt along with some detail(not sure) about the linking errors. If the user chooses to answer no, display the message "You can always run 'port rev-upgrade' later to fix this".
-
-Question type: A yes/no question seems to handle the situation well. The whole list will be rebuilt as asking for each port might break the process of rev-upgrade. 
-
-Example-
-{{{
-$> port rev-upgrade
-The following ports will be rebuilt:
-  boofar @0.0.1 +xzy
-  barfoo @0.0.2 +xzy
-  foba @0.1
-Continue? [Y/n]: Y
----> Rebuilding boofar @0.0.1 +xzy
----> Rebuilding barfoo @0.0.2 +xzy
----> Rebuilding foba @0.1 
 $>
 }}}
@@ -192 +132 @@
 }}}
 
-=== Choose variants interactively ===
+=== Variant specific dependency (Low-priority) ===
+Desc: When installing a port that requires a dependency to have a certain variant, but this variant is not set. Ask the user if it should reinstall the dependency with that variant. This interaction is currently marked low priority.
+
+Message: A warning message explaining that reinstalling with a specific variant could break any already-installed dependents that relied on the previously-selected variants.
+
+Question type: A yes/no question is suitable here. The correct variant will be selected and installed automatically so no need to provide options. 
+
+Example-
+{{{
+$> port install foobar
+The package 'foobar +quartz' requires 'barfoo +quartz' but 'barfoo' is installed.
+Warning: Reinstalling with a specific variant could break any already-installed dependents that relied on the previously-selected variants.
+Do you wish to install barfoo +quartz? [Y/n]: Y
+---> Installing barfoo @1.0.1 +xzy
+——-> Installing foobar
+$>
+}}}
+
+=== Choose variants interactively (Low-priority) ===
 Desc: When installing a port the user can be given a list of all the variants of the port they wish to install and they can select them interactively. This interaction is currently flagged low priority.
 
@@ -211 +169 @@
 }}}
 
+= Use Cases Completed =
+
+=== Rebuilding in rev-upgrade ===
+Desc: Before rebuilding any port in rev-upgrade the user will be asked for confirmation.
+
+Message: A list of ports that will be rebuilt along with some detail(not sure) about the linking errors. If the user chooses to answer no, display the message "You can always run 'port rev-upgrade' later to fix this".
+
+Question type: A yes/no question seems to handle the situation well. The whole list will be rebuilt as asking for each port might break the process of rev-upgrade. 
+
+Example-
+{{{
+$> port rev-upgrade
+The following ports will be rebuilt:
+  boofar @0.0.1 +xzy
+  barfoo @0.0.2 +xzy
+  foba @0.1
+Continue? [Y/n]: Y
+---> Rebuilding boofar @0.0.1 +xzy
+---> Rebuilding barfoo @0.0.2 +xzy
+---> Rebuilding foba @0.1 
+$>
+}}}
+
+=== Apt-get like behaviour ===
+Desc: When installing a port, list all the dependencies and ask the user for confirmation just like apt-get does.
+
+Message: A list of all the dependencies.
+
+Question type: A continue/abort question to give the options of continuing with the installation or aborting it. This could even use a 10s timeout, giving an option to abort during the timeout and continuing automatically after the time is out.
+
+Example-
+{{{
+$> port install foobar
+The following dependencies of foobar will be installed:
+  boofar @0.0.1 +xzy
+  barfoo @0.0.2 +xzy
+  foba @0.1
+Continue? [Y/n]: Y
+---> Installing boofar @0.0.1 +xzy
+---> Installing barfoo @0.0.2 +xzy
+---> Installing foba @0.1
+---> Installing foobar
+$>
+}}}
+
 = Implementation Details =