Jan 2022 - 1.8.7
- Bugfix: Removed the hamlib test from the KLog start that was causing big delays.
- Bugfix: Serial speed was not saved to config file.
- Bugfix: eQSL Uploads problem solved (Closes#406).
- Bugfix: Connection to the radios were not being done properly (Closes#407) (Closes#379).
- Bugfix: SplitCheckBox was checked when coming from Setup (Closes#377).
- Bugfix: Entering a QRZ cleared the DX Gridsquare if it was previously entered (Closes#357).
- Bugfix: Imported QSOs add the default electronic QSL send info if configured.
- Bugfix: DXCC widget shows last Entity status after modifying a QSO (Closes#412).
- Bugfix: Hamlib is now stopped while editing a QSO (Closes#414).
- Bugfix: Hamlib on serial devices works ok. (Closes#355).
- Bugfix: RST is not changed on mode change when editing. (Closes#423).
- New feature: Added a Manual Mode checkbox to disable quickly hamlib & wsjtx integration.
- New feature: Added "Save" and "Cancel" button when editing a recorded QSO.
- Update: Developers mailing list address changed to klog@groups.io (Closes#421).
Reported by: portscout
This is the FreeBSD Ports Collection. For an easy to use
WEB-based interface to it, please see:
https://www.FreeBSD.org/ports
For general information on the Ports Collection, please see the
FreeBSD Handbook ports section which is available from:
https://docs.freebsd.org/en/books/handbook/ports/
for the latest official version
or:
The ports(7) manual page (man ports).
These will explain how to use ports and packages.
If you would like to search for a port, you can do so easily by
saying (in /usr/ports):
make search name="<name>"
or:
make search key="<keyword>"
which will generate a list of all ports matching <name> or <keyword>.
make search also supports wildcards, such as:
make search name="gtk*"
For information about contributing to FreeBSD ports, please see the Porter's
Handbook, available at:
https://docs.freebsd.org/en/books/porters-handbook/
NOTE: This tree will GROW significantly in size during normal usage!
The distribution tar files can and do accumulate in /usr/ports/distfiles,
and the individual ports will also use up lots of space in their work
subdirectories unless you remember to "make clean" after you're done
building a given port. /usr/ports/distfiles can also be periodically
cleaned without ill-effect.