Next | Query returned 25 messages, browsing 21 to 30 | previous

History of commit frequency

CVS Commit History:


   2005-12-05 21:51:20 by Roland Illig | Files touched by this commit (1432)
Log message:
Fixed pkglint warnings. The warnings are mostly quoting issues, for
example MAKE_ENV+=FOO=${BAR} is changed to MAKE_ENV+=FOO=${BAR:Q}. Some
other changes are outlined in

    http://mail-index.netbsd.org/tech-pkg/2005/12/02/0034.html
   2005-12-04 16:49:45 by Dan McMahill | Files touched by this commit (1)
Log message:
override the do-patch target.  This is just the meta-pkg and we're not
extracting anything, but the patches for the other wcalc packages all live
in this common spot.  Fixes recently noted build problems.
   2005-12-02 00:58:16 by Dan McMahill | Files touched by this commit (3)
Log message:
define a common patch directory for the wcalc packages
   2005-11-19 16:37:08 by Roland Illig | Files touched by this commit (2)
Log message:
Fixed pkglint warnings:
- Replaced #defined with #none for EXTRACT_ONLY.
- Replaced #defined with yes for NO_BUILD, NO_CONFIGURE, NO_MTREE.
- Removed NO_CHECKSUM completely, as a distinfo file exists, it has the
  correct checksums, and I couldn't find even a hint to why NO_CHECKSUM
  was set.
   2005-11-01 04:54:45 by Dan McMahill | Files touched by this commit (5) | Imported package
Log message:
import wcalc-0.9

Wcalc is a transmission line analysis and synthesis tool.  Several
structures including air core solenoid inductors, coaxial cable,
single and coupled microstrip, stripline, and metal-insulator-
semiconductor microstrip are included.

Wcalc can analyze the electrical parameters for a given physical
description of the structure or synthesize the required dimensions
to meet certain desired electrical characteristics.

Wcalc provides several different frontends for accessing the numeric
engine.  Currently, there is a GTK based standalone graphical
user interface, a common gateway interface (CGI) for web access,
Scilab, Octave, and Matlab interfaces for maximum flexibility within
a scientific programming environment, and a standard input/output
(stdio) interface which allows a simple interface to other 3rd
party tools which can communicate via a pipe.

The different frontends are installed as different packages for
flexibility in deployment.


Next | Query returned 25 messages, browsing 21 to 30 | previous