Problems found with existing distfile for eagle:
distfiles/eagle-lin32-7.4.0.run
No changes made to eagle/distinfo file.
Otherwise, existing SHA1 digests verified and found to be the same on
the machine holding the existing distfiles (morden). All existing
SHA1 digests retained for now as an audit trail.
then automatically generate a PLIST that says "${PKGNAME} has no files".
* If PLIST_SRC and GENERATE_PLIST are not set in a package Makefile,
and no PLIST files exist, then fail during the package build with
PKG_FAIL_REASON.
* Remove "intentionally empty" PLISTs again.
Now, the easy way to say that a package installs no files is to just
add the following to the package Makefile:
PLIST_SRC= # empty
that directly manipulate empty PLISTs.
Modify plist/plist.mk so that if the PLIST files are missing and no
GENERATE_PLIST is defined, then the package fails to build.
- fixes a bug in the cgi frontend for coupled microstrip which caused
lots of bad warning messages.
- replaces the alert dialog box with a log window which prevents multiple
alert windows from appearing.
- 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.
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.