RubyGems - portvcs - Versions diffs - 0.0.1 → 0.0.2 - Mend

portvcs 0.0.1 → 0.0.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (6) hide show

data/README.rdoc CHANGED Viewed

@@ -18,7 +18,7 @@ At the time of writing FreeBSD uses CVS (jeez) for its ports collection,
 so portvcs (with default configuration) connects to well-known French
 CVS server via TCP port 2401 and reads the logs of a particular port.
 By default the utility constrains the history to 1 year but that's easy
-changeable via +-d+ CL (command line) option.
+changeable via <tt>-d</tt> CL (command line) option.
 portvcs isn't restricted to FreeBSD ports--it can read logs from
 (probably) any CVS server but in that case its usefulness is very
@@ -33,13 +33,13 @@ The options are as follows:
                             configuration file. The first found wins.
 --config NAME::             The name of the configuration file. If
-                            it contains +/+ in it, the list from
-                            <tt>\--config-dirs</tt> is ignored.
+                            it contains <tt>/</tt> in it, the list from
+                            <tt>--config-dirs</tt> is ignored.
 -d EXP::                     Passes the EXP to VCS server to set limits
                              for the logs. Usually it's something like
                              '2 months ago<'. For all possible values,
-                             read the help for the option +-d+ in cvs
+                             read the help for the option <tt>-d</tt> in cvs
                              help for its log command, e.g, type:
                               % info -n '(cvs)log options'
@@ -58,8 +58,9 @@ The options are as follows:
 --ports-tree DIR::          A directory that follows CVSROOT and serves
                             as a ports tree. For example, CVSROOT can
-                            be +/home/ncvs+ and the ports directory can
-                            be +ports+ or may be empty at all.
+                            be <tt>/home/ncvs</tt> and the ports
+                            directory can be <tt>ports</tt> or may be
+                            empty at all.
 --vcs-version::             Just get version of a remote VCS server and
                             exit.
@@ -70,7 +71,8 @@ The options are as follows:
 -V::                         Show portvcs version and exit.
 -v::                         Be more verbose. You can supply it several
-                             times, viz. +-vv+ dumps even more debug info.
+                             times, viz. <tt>-vv</tt> dumps even more
+                             debug info.
 ==Configuration
@@ -79,9 +81,9 @@ portvcs looks for its configuration at 3 places at start up.
 1. At <tt>PORTVCS_CONF</tt> env variable. (Its format is exactly similar
    to CL options.)
-2. At configuration file. Its default name is <tt>portvcs.yaml</tt> and
-   it can be stored in several system directories which are observable
-   by <tt>--config--dirs</tt> CL option.
+2. At the configuration file. Its default name is <tt>portvcs.yaml</tt>
+   and it can be stored in several system directories which are
+   observable by <tt>--config--dirs</tt> CL option.
 3. At command line.
@@ -91,6 +93,12 @@ The configuration file must be in YAML format. Look into <tt>`gem env
 gemdir`/gems/portvcs-x.y.z/etc/</tt> directory for samples.
+==Environment
+PAGER::           Output from the VCS server goes here.
+PORTVCS_CONF::    See Configuration.
 ==Examples
  % portvcs www/firefox

data/bin/portvcs CHANGED Viewed

@@ -44,6 +44,10 @@ def errx(ec, t)
   exit ec if ec > 0
 end
+def warnx(t)
+  STDERR.puts File.basename($0) + ' warning: ' + t.to_s
+end
 def cl_parse(myargs, times = 1)
   o = OptionParser.new()
   o.banner = $conf[:banner]
@@ -133,6 +137,7 @@ end
 # 4. connect to remote VCS
 v = VCS.new($conf[:vcs])
+out = STDOUT
 begin
   v.open(debug: ($conf[:verbose] >= 2 ? true : false), host: $conf[:host], cvsroot: $conf[:cvsroot],
          port: $conf[:port], user: $conf[:user], pass: $conf[:pass],
@@ -147,18 +152,27 @@ begin
       end
       p[1] = 'Makefile' if !p[1]
+      try2retry = true
       out = pager_setup() || STDOUT # get output stream
       vp.log(p[0], p[1], $conf[:date_cond]) {|i|
         begin
           out.puts i
-        rescue Errno::EPIPE
+        rescue Errno::EPIPE # problem with pager
+          out.close unless out == STDOUT
           out = STDOUT
-          retry
+          if try2retry
+            try2retry = false
+            warnx('cannot popen with pager, retrying with stdout')
+            retry
+          else
+            raise
+          end
         end
       }
-      out.close unless out == STDOUT
     end
   }
 rescue
   errx(1, $!)
+ensure
+  out.close unless out == STDOUT
 end

data/doc/NEWS ADDED Viewed

@@ -0,0 +1,3 @@
+=== 0.0.2
+- Fixed a bug with PAGER env.

data/doc/README.rdoc CHANGED Viewed

@@ -18,7 +18,7 @@ At the time of writing FreeBSD uses CVS (jeez) for its ports collection,
 so portvcs (with default configuration) connects to well-known French
 CVS server via TCP port 2401 and reads the logs of a particular port.
 By default the utility constrains the history to 1 year but that's easy
-changeable via +-d+ CL (command line) option.
+changeable via <tt>-d</tt> CL (command line) option.
 portvcs isn't restricted to FreeBSD ports--it can read logs from
 (probably) any CVS server but in that case its usefulness is very
@@ -33,13 +33,13 @@ The options are as follows:
                             configuration file. The first found wins.
 --config NAME::             The name of the configuration file. If
-                            it contains +/+ in it, the list from
-                            <tt>\--config-dirs</tt> is ignored.
+                            it contains <tt>/</tt> in it, the list from
+                            <tt>--config-dirs</tt> is ignored.
 -d EXP::                     Passes the EXP to VCS server to set limits
                              for the logs. Usually it's something like
                              '2 months ago<'. For all possible values,
-                             read the help for the option +-d+ in cvs
+                             read the help for the option <tt>-d</tt> in cvs
                              help for its log command, e.g, type:
                               % info -n '(cvs)log options'
@@ -58,8 +58,9 @@ The options are as follows:
 --ports-tree DIR::          A directory that follows CVSROOT and serves
                             as a ports tree. For example, CVSROOT can
-                            be +/home/ncvs+ and the ports directory can
-                            be +ports+ or may be empty at all.
+                            be <tt>/home/ncvs</tt> and the ports
+                            directory can be <tt>ports</tt> or may be
+                            empty at all.
 --vcs-version::             Just get version of a remote VCS server and
                             exit.
@@ -70,7 +71,8 @@ The options are as follows:
 -V::                         Show portvcs version and exit.
 -v::                         Be more verbose. You can supply it several
-                             times, viz. +-vv+ dumps even more debug info.
+                             times, viz. <tt>-vv</tt> dumps even more
+                             debug info.
 ==Configuration
@@ -79,9 +81,9 @@ portvcs looks for its configuration at 3 places at start up.
 1. At <tt>PORTVCS_CONF</tt> env variable. (Its format is exactly similar
    to CL options.)
-2. At configuration file. Its default name is <tt>portvcs.yaml</tt> and
-   it can be stored in several system directories which are observable
-   by <tt>--config--dirs</tt> CL option.
+2. At the configuration file. Its default name is <tt>portvcs.yaml</tt>
+   and it can be stored in several system directories which are
+   observable by <tt>--config--dirs</tt> CL option.
 3. At command line.
@@ -91,6 +93,12 @@ The configuration file must be in YAML format. Look into <tt>`gem env
 gemdir`/gems/portvcs-x.y.z/etc/</tt> directory for samples.
+==Environment
+PAGER::           Output from the VCS server goes here.
+PORTVCS_CONF::    See Configuration.
 ==Examples
  % portvcs www/firefox

data/lib/portvcs/meta.rb CHANGED Viewed

@@ -1,6 +1,6 @@
 module PortVCS
   module Meta
     NAME = 'portvcs'
-    VERSION = '0.0.1'
+    VERSION = '0.0.2'
   end
 end

metadata CHANGED Viewed

@@ -5,8 +5,8 @@ version: !ruby/object:Gem::Version
   segments:
   - 0
   - 0
-  - 1
-  version: 0.0.1
+  - 2
+  version: 0.0.2
 platform: ruby
 authors:
 - Alexander Gromnitsky
@@ -14,7 +14,7 @@ autorequire:
 bindir: bin
 cert_chain: []
-date: 2010-12-13 00:00:00 +02:00
+date: 2010-12-15 00:00:00 +02:00
 default_executable: portvcs
 dependencies:
 - !ruby/object:Gem::Dependency
@@ -42,6 +42,7 @@ extra_rdoc_files:
 - doc/TODO
 - doc/README.rdoc
 - doc/LICENSE
+- doc/NEWS
 files:
 - lib/portvcs/portvcs.rb
 - lib/portvcs/utils.rb
@@ -50,6 +51,7 @@ files:
 - doc/TODO
 - doc/README.rdoc
 - doc/LICENSE
+- doc/NEWS
 - etc/portvcs.yaml
 - etc/fr.FreeBSD.org.yaml
 - README.rdoc