Changeset 315 in tailor for README

Timestamp:

05/23/05 16:15:46 (8 years ago)

Author:

lele@…

Hash name:

20050523141546-97f81-316eb82b8236d5e403581507651e4f4863e7b767

Message:

Reworked the interactive session, separating configuration from state

File:

• README (modified) (2 diffs)

README

@@ -46 +46 @@
 .. _baazar-ng: http://www.bazaar-ng.org/
 
+
 Installation
 ============
@@ -204 +205 @@
 
 
+Interactive sessions
+--------------------
+
+Tailor offers an alternative way of driving its activity by using an
+interactive session, bringing the configuration more similar to a
+script.
+
+Although this is still a work-in-progress, it's quickly becoming my
+preferred usage, as its functionality cover the underlying tailor
+features.
+
+For example, this is the script I'm using to test it::
+
+    cd /tmp/p/wc
+    state_file tailor.state
+    source_kind darcs
+    target_kind svn
+    source_repository /home/lele/WiP/cvsync
+    sub_directory cvsync
+
+that, as you can see, specifies the context needed by tailor to do its
+work. With the following command line::
+
+    $ tailor.py --verbose --interactive tailor.cmds
+    Welcome to the Tailor interactive session: you can issue several commands
+    with the usual `readline` facilities. With "help" you'll get a list of
+    available commands.
+
+    Current directory: /tmp/p/wc
+    Current state file: /tmp/p/wc/tailor.state
+    Current source kind: darcs
+    Current target kind: svn
+    Current source repository: /home/lele/WiP/cvsync
+    Sub directory: cvsync
+    tailor $ help
+    
+    Documented commands (type help <topic>):
+    ========================================
+    EOF                get_changes   source_module      target_module
+    bootstrap          logfile       source_repository  target_repository
+    cd                 save          state_file
+    current_directory  show_changes  sub_directory
+    exit               source_kind   target_kind
+
+    Undocumented commands:
+    ======================
+    help
+
+    tailor $ help bootstrap
+    
+        Checkout the initial upstream revision, by default HEAD (or
+        specified by argument), then import the subtree into the
+        target repository.
+
+
 Further help
 ============