[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

gEDA-bug: [Bug 713968] [NEW] don't output backend configuration on every run of gsch2pcb



Public bug reported:

Traditionally, gsc2pcb outputs lots of lines, that can safely be
ignored. This is clearly, newbie unfriendly, since it requires
experience to spot the real issues between the benign warnings. I
propose to reduce the spew at default verbosity level.

One of them is:
=====================================================
gsch2pcb backend configuration:

   ----------------------------------------
   Variables which may be changed in gafrc:
   ----------------------------------------
   gsch2pcb:pcb-m4-command:    /usr/bin/m4
   gsch2pcb:pcb-m4-dir:        /usr/local/share/pcb/m4
   gsch2pcb:pcb-m4-confdir:    /usr/local/etc/pcb
   gsch2pcb:pcb-m4-path:       /usr/local/share/pcb/m4  /usr/local/etc/pcb  $HOME/.pcb  .
   gsch2pcb:m4-command-line:   /usr/bin/m4 -d  -I/usr/local/share/pcb/m4 -I/usr/local/etc/pcb -I$HOME/.pcb -I. /usr/local/share/pcb/m4/common.m4 - >> phasendetektor-atlas.new.pcb

   ---------------------------------------------------
   Variables which may be changed in the project file:
   ---------------------------------------------------
   gsch2pcb:use-m4:            no

=====================================================

This information is most likely only useful when setting up some special
m4 environment. There is no much point in telling it each and every time
gsche2pcb is called.

Suggestion: Only output the notes on backend configuration if the option
--verbose was used.

---<)kaimartin(>---

** Affects: geda
     Importance: Undecided
         Status: New


** Tags: gnetlist

** Tags added: gnetlist

-- 
You received this bug notification because you are a member of gEDA Bug
Team, which is subscribed to gEDA.
https://bugs.launchpad.net/bugs/713968

Title:
  don't output backend configuration on every run of gsch2pcb

Status in GPL Electronic Design Automation tools:
  New

Bug description:
  Traditionally, gsc2pcb outputs lots of lines, that can safely be
  ignored. This is clearly, newbie unfriendly, since it requires
  experience to spot the real issues between the benign warnings. I
  propose to reduce the spew at default verbosity level.

  One of them is:
  =====================================================
  gsch2pcb backend configuration:

     ----------------------------------------
     Variables which may be changed in gafrc:
     ----------------------------------------
     gsch2pcb:pcb-m4-command:    /usr/bin/m4
     gsch2pcb:pcb-m4-dir:        /usr/local/share/pcb/m4
     gsch2pcb:pcb-m4-confdir:    /usr/local/etc/pcb
     gsch2pcb:pcb-m4-path:       /usr/local/share/pcb/m4  /usr/local/etc/pcb  $HOME/.pcb  .
     gsch2pcb:m4-command-line:   /usr/bin/m4 -d  -I/usr/local/share/pcb/m4 -I/usr/local/etc/pcb -I$HOME/.pcb -I. /usr/local/share/pcb/m4/common.m4 - >> phasendetektor-atlas.new.pcb

     ---------------------------------------------------
     Variables which may be changed in the project file:
     ---------------------------------------------------
     gsch2pcb:use-m4:            no

  =====================================================

  This information is most likely only useful when setting up some
  special m4 environment. There is no much point in telling it each and
  every time gsche2pcb is called.

  Suggestion: Only output the notes on backend configuration if the
  option --verbose was used.

  ---<)kaimartin(>---




_______________________________________________
geda-bug mailing list
geda-bug@xxxxxxxxxxxxxx
http://www.seul.org/cgi-bin/mailman/listinfo/geda-bug