File: 090_gsat_README.diff

package info (click to toggle)
predict 2.2.3-4
  • links: PTS
  • area: main
  • in suites: jessie, jessie-kfreebsd, stretch
  • size: 4,712 kB
  • ctags: 1,623
  • sloc: ansic: 19,433; sh: 3,518; makefile: 429; yacc: 318; perl: 82
file content (13 lines) | stat: -rw-r--r-- 1,654 bytes parent folder | download | duplicates (3)
1
2
3
4
5
6
7
8
9
10
11
12
13
Index: predict-2.2.3/clients/gsat-1.1.0/README
===================================================================
--- predict-2.2.3.orig/clients/gsat-1.1.0/README	2009-11-14 10:27:34.000000000 -0500
+++ predict-2.2.3/clients/gsat-1.1.0/README	2009-11-14 10:28:21.000000000 -0500
@@ -39,7 +39,7 @@
 ABOUT PLUGINS
 -------------
 
-gsat can do automatic doppler correction and rotor control via plugins. Plugins are placed in the /usr/local/lib/gsat/plugins directory by default. You can override this setting the GSATPLUGINSDIR environment variable. Plugin's name must begin by "radio_" for the radio plugins and "rotor_" for the rotor plugins. Once you have the plugins installed, you can select it in the preferences window, pass it a config string and activate it in the doppler section of the main window.
+gsat can do automatic doppler correction and rotor control via plugins. Plugins are placed in the /usr/lib/gsat/plugins directory by default. You can override this setting the GSATPLUGINSDIR environment variable. Plugin's name must begin by "radio_" for the radio plugins and "rotor_" for the rotor plugins. Once you have the plugins installed, you can select it in the preferences window, pass it a config string and activate it in the doppler section of the main window.
 There is a file called Plugin_API with the info to program a custom plugin. There are some examples in the plugins subdir.
 Please note that not all the plugins in the plugins directory of this package are in a working state. I'm working on some of them and it is possible that even some refuse to compile. I include them to show some examples of plugin programming.