Drop documentation references to aprsg, it's been a bit unmaintained for a while.

This commit is contained in:
Heikki Hannikainen 2015-10-13 10:29:40 +03:00
parent 35fe3cd580
commit 3e298b0f81
3 changed files with 3 additions and 3 deletions

View File

@ -119,7 +119,7 @@ Ideas that have been suggested, but will not be added
--------------------------------------------------------
* igating and other radio interfaces: These are igate functions, and
should be implemented in igate software (aprsg, aprx, there are a lot
should be implemented in igate software (aprx, aprs4r, there are a lot
of those - pick one and implement it there).
* beacon generation: Most if not all igate software can already beacon
objects. No need to reimplement the functionality here.

View File

@ -32,7 +32,7 @@ object generation. The idea is to keep aprsc relatively simple and lean,
and leave the more specialized features for more specialized software.
If you need a nice, compact igate software for Linux, please take a look at
either aprsg, aprx, or aprs4r. If you need to run an APRS-IS server on some
either aprx, or aprs4r. If you need to run an APRS-IS server on some
platform not supported by aprsc, or if you need the features existing in
javAPRSSrvr which are missing from aprsc, javAPRSSrvr is the right choice
for you - it's got a lot of good features that many of you need, and it

View File

@ -65,7 +65,7 @@ object generation. The idea is to keep aprsc relatively simple and lean,
and leave the more specialized features for more specialized software.
If you need a nice, compact igate software for Linux, please take a look at
either aprsg, aprx, or aprs4r. If you need to run an APRS-IS server on
either aprx or aprs4r. If you need to run an APRS-IS server on
Windows or some other platform not supported by aprsc, or if you need the
features existing in javAPRSSrvr which are missing from aprsc, javAPRSSrvr
is the right choice for you - it's got a lot of good features that many of