[chirp_devel] [PATCH] Adding INSTALL, README, and README.support files
Adding these files to satisfy #122
# HG changeset patch # User David Griffith dave@661.org # Date 1336528109 25200 # Node ID e5324579e0944f2cb59c30b5bfda6f5b4caf2ac7 # Parent 3f573d4f142983971b8bcaa7ba38e43cc29a6372 Adding INSTALL, README, and README.support
diff -r 3f573d4f1429 -r e5324579e094 INSTALL --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/INSTALL Tue May 08 18:48:29 2012 -0700 @@ -0,0 +1,44 @@ +This file describes the installation of Chirp without package management +on Linux and other Unix-like operating systems. This sort of thing may +be your only choice because 1) a package has not yet been made for your +OS or distribution, 2) the packaged version is obsolete, or 3) you want +to try a daily build. + + +For Debian, Ubuntu, and related systems, the following packages are required: +python +python-gtk2 +python-libxml2 +python-libxslt1 +python-serial +python-support + +For Redhat, Fedora, CentOS and related systems, the following packages +are required: (This list is incomplete. Please submit corrections.) +python +pygtk2 +libxml2-python +python-libxslt + + +Once these packages are installed, you can run Chirp directly from the +distribution directory by typing "./chirpw". If you want to install it +properly, type this: + + sudo python setup.py install --record files.txt + +This will install the package and create a list of files that were +added to your system. If you want to deinstall Chirp, type this: + + sudo xargs -0 rm -rf < files.txt + +This will cause rm(1) to take its list of arguments from the file named +"files.txt" and remove those files from the system. If you forgot to +create "files.txt", you can simply reinstall the way it is shown here +and continue on your way. + +Note: This will not uninstall directories created by the installation of +Chirp. Presence of these empty directories shouldn't be a problem, but +if they are, it's easy to go through the files.txt file, identify them, +and remove them. + diff -r 3f573d4f1429 -r e5324579e094 README --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/README Tue May 08 18:48:29 2012 -0700 @@ -0,0 +1,10 @@ +Chirp is a free, open-source, multiplatform tool for programming your +amateur radio. It supports a large number of manufacturers and models, +as well as provides a way to interface with multiple data sources and +formats. + +Complete documentation may be found at the Chirp website at +http://chirp.danplanet.com/projects/chirp + +For a list of radios supported by Chirp, see the file "README.support" + diff -r 3f573d4f1429 -r e5324579e094 README.support --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/README.support Tue May 08 18:48:29 2012 -0700 @@ -0,0 +1,67 @@ +Alinco + DR-03T + DR-06T + DR135T + DR235T + DR435T + DJ596T + +Baofeng + UV-3R + UV-5R (in daily builds) + +Icom + IC-2820H + ID-800H + ID-880H + IC-2200H + IC-91/92AD + IC-V/U82 + ID-RP2000V/RP4000V/RP2V/RP2D + IC-2100H + IC-2720H + IC-T70 + IC-Q7A + IC-W32A + IC-7200 + IC-7000 + ID-31A + +Jetstream + JT220M + +Kenwood + TH-D7A/G + TH-D72 + TH-F6A + TH-K2 + TM-271A + TM-D700 + TM-D710 + TM-G707 (in daily builds) + TM-V7A + TM-V71A + +Puxing + PX-2R (UHF) + PX-777 + +Yaesu + FT-60R + FT-817/ND + FT-857/D + FT-897 + FT-2800M + FT-7800R + FT-7900R + FT-8800R + FT-8900R + VX-3R + VX-5R + VX-6R + VX-7R + VX-8R + +Wouxun + KG-UVD1P/UV2D/UV3D +
I don't think README.support should be distributed like this. I'd prefer to give them a script that will output the current list, so we don't have to maintain another file.
Tom KD7LXL On May 8, 2012 7:52 PM, "David Griffith" dave@661.org wrote:
Adding these files to satisfy #122
# HG changeset patch # User David Griffith dave@661.org # Date 1336528109 25200 # Node ID e5324579e0944f2cb59c30b5bfda6f5b4caf2ac7 # Parent 3f573d4f142983971b8bcaa7ba38e43cc29a6372 Adding INSTALL, README, and README.support
diff -r 3f573d4f1429 -r e5324579e094 INSTALL --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/INSTALL Tue May 08 18:48:29 2012 -0700 @@ -0,0 +1,44 @@ +This file describes the installation of Chirp without package management +on Linux and other Unix-like operating systems. This sort of thing may +be your only choice because 1) a package has not yet been made for your +OS or distribution, 2) the packaged version is obsolete, or 3) you want +to try a daily build.
+For Debian, Ubuntu, and related systems, the following packages are required: +python +python-gtk2 +python-libxml2 +python-libxslt1 +python-serial +python-support
+For Redhat, Fedora, CentOS and related systems, the following packages +are required: (This list is incomplete. Please submit corrections.) +python +pygtk2 +libxml2-python +python-libxslt
+Once these packages are installed, you can run Chirp directly from the +distribution directory by typing "./chirpw". If you want to install it +properly, type this:
- sudo python setup.py install --record files.txt
+This will install the package and create a list of files that were +added to your system. If you want to deinstall Chirp, type this:
- sudo xargs -0 rm -rf < files.txt
+This will cause rm(1) to take its list of arguments from the file named +"files.txt" and remove those files from the system. If you forgot to +create "files.txt", you can simply reinstall the way it is shown here +and continue on your way.
+Note: This will not uninstall directories created by the installation of +Chirp. Presence of these empty directories shouldn't be a problem, but +if they are, it's easy to go through the files.txt file, identify them, +and remove them.
diff -r 3f573d4f1429 -r e5324579e094 README --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/README Tue May 08 18:48:29 2012 -0700 @@ -0,0 +1,10 @@ +Chirp is a free, open-source, multiplatform tool for programming your +amateur radio. It supports a large number of manufacturers and models, +as well as provides a way to interface with multiple data sources and +formats.
+Complete documentation may be found at the Chirp website at +http://chirp.danplanet.com/projects/chirp
+For a list of radios supported by Chirp, see the file "README.support"
diff -r 3f573d4f1429 -r e5324579e094 README.support --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/README.support Tue May 08 18:48:29 2012 -0700 @@ -0,0 +1,67 @@ +Alinco
- DR-03T
- DR-06T
- DR135T
- DR235T
- DR435T
- DJ596T
+Baofeng
- UV-3R
- UV-5R (in daily builds)
+Icom
- IC-2820H
- ID-800H
- ID-880H
- IC-2200H
- IC-91/92AD
- IC-V/U82
- ID-RP2000V/RP4000V/RP2V/RP2D
- IC-2100H
- IC-2720H
- IC-T70
- IC-Q7A
- IC-W32A
- IC-7200
- IC-7000
- ID-31A
+Jetstream
- JT220M
+Kenwood
- TH-D7A/G
- TH-D72
- TH-F6A
- TH-K2
- TM-271A
- TM-D700
- TM-D710
- TM-G707 (in daily builds)
- TM-V7A
- TM-V71A
+Puxing
- PX-2R (UHF)
- PX-777
+Yaesu
- FT-60R
- FT-817/ND
- FT-857/D
- FT-897
- FT-2800M
- FT-7800R
- FT-7900R
- FT-8800R
- FT-8900R
- VX-3R
- VX-5R
- VX-6R
- VX-7R
- VX-8R
+Wouxun
- KG-UVD1P/UV2D/UV3D
chirp_devel mailing list chirp_devel@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_devel
I don't think README.support should be distributed like this. I'd prefer to give them a script that will output the current list, so we don't have to maintain another file.
I agree, and I think I said that in the last round where this was presented. The "make_supported.py" script already does this (and much more), so I'd rather have the file say "run that if you're interested".
On Wed, May 9, 2012 at 7:30 AM, Dan Smith dsmith@danplanet.com wrote:
I don't think README.support should be distributed like this. I'd prefer to give them a script that will output the current list, so we don't have to maintain another file.
I agree, and I think I said that in the last round where this was presented. The "make_supported.py" script already does this (and much more), so I'd rather have the file say "run that if you're interested".
I wouldn't mind instructions for how to run this in the README. I always forget :-)
Tom KD7LXL
On Wed, 9 May 2012, Tom Hayward wrote:
On Wed, May 9, 2012 at 7:30 AM, Dan Smith dsmith@danplanet.com wrote:
I don't think README.support should be distributed like this. I'd prefer to give them a script that will output the current list, so we don't have to maintain another file.
I agree, and I think I said that in the last round where this was presented. The "make_supported.py" script already does this (and much more), so I'd rather have the file say "run that if you're interested".
I wouldn't mind instructions for how to run this in the README. I always forget :-)
Okay, here's an updated patch. README.support is eliminated and README has instructions to run "python share/make_supported.py > radios.html".
# HG changeset patch # User David Griffith dave@661.org # Date 1336591163 25200 # Node ID e2857fd2d5e7c41d522f3d31fa291986055ad9cb # Parent 24cb2e48098df646010797cdd3e4664f6b6513c5 New README and INSTALL files
diff -r 24cb2e48098d -r e2857fd2d5e7 INSTALL --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/INSTALL Wed May 09 12:19:23 2012 -0700 @@ -0,0 +1,44 @@ +This file describes the installation of Chirp without package management +on Linux and other Unix-like operating systems. This sort of thing may +be your only choice because 1) a package has not yet been made for your +OS or distribution, 2) the packaged version is obsolete, or 3) you want +to try a daily build. + + +For Debian, Ubuntu, and related systems, the following packages are required: +python +python-gtk2 +python-libxml2 +python-libxslt1 +python-serial +python-support + +For Redhat, Fedora, CentOS and related systems, the following packages +are required: (This list is incomplete. Please submit corrections.) +python +pygtk2 +libxml2-python +python-libxslt + + +Once these packages are installed, you can run Chirp directly from the +distribution directory by typing "./chirpw". If you want to install it +properly, type this: + + sudo python setup.py install --record files.txt + +This will install the package and create a list of files that were +added to your system. If you want to deinstall Chirp, type this: + + sudo xargs -0 rm -rf < files.txt + +This will cause rm(1) to take its list of arguments from the file named +"files.txt" and remove those files from the system. If you forgot to +create "files.txt", you can simply reinstall the way it is shown here +and continue on your way. + +Note: This will not uninstall directories created by the installation of +Chirp. Presence of these empty directories shouldn't be a problem, but +if they are, it's easy to go through the files.txt file, identify them, +and remove them. + diff -r 24cb2e48098d -r e2857fd2d5e7 README --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/README Wed May 09 12:19:23 2012 -0700 @@ -0,0 +1,16 @@ +Chirp is a free, open-source, multiplatform tool for programming your +amateur radio. It supports a large number of manufacturers and models, +as well as provides a way to interface with multiple data sources and +formats. + +Complete documentation may be found at the Chirp website at +http://chirp.danplanet.com/projects/chirp + +For a list of radios supported by Chirp, type the following command: + + python share/make_supported.py > radios.html + +This will generate an HTML file containing a rundown of all the +currently supported radios and a matrix of what features are supported +for which radio. +
Okay, here's an updated patch. README.support is eliminated and README has instructions to run "python share/make_supported.py > radios.html".
Looks okay to me. Thanks for making those changes. I'll wait for Tom to ack since he had comments in this thread.
On Wed, May 9, 2012 at 1:36 PM, Dan Smith dsmith@danplanet.com wrote:
Okay, here's an updated patch. README.support is eliminated and README has instructions to run "python share/make_supported.py > radios.html".
Looks okay to me. Thanks for making those changes. I'll wait for Tom to ack since he had comments in this thread.
I much prefer the updated version to the static README.support file.
The only remaining issue I see is that the 0.3.0/default branch now depends on python-suds for Debian/Ubuntu (not sure of the Fedora equivalent.
Tom
On Wed, 9 May 2012, Tom Hayward wrote:
On Wed, May 9, 2012 at 1:36 PM, Dan Smith dsmith@danplanet.com wrote:
Okay, here's an updated patch. README.support is eliminated and README has instructions to run "python share/make_supported.py > radios.html".
Looks okay to me. Thanks for making those changes. I'll wait for Tom to ack since he had comments in this thread.
I much prefer the updated version to the static README.support file.
The only remaining issue I see is that the 0.3.0/default branch now depends on python-suds for Debian/Ubuntu (not sure of the Fedora equivalent.
Weird. I don't have python-suds installed, yet Chirp seems to work just fine. What part of the code depends on python-suds?
Weird. I don't have python-suds installed, yet Chirp seems to work just fine. What part of the code depends on python-suds?
Well, it doesn't depend on it, in the strict sense of the word.
The radioreference driver uses it, but gracefully handles the case where it's missing. Since it's available on debian, there's not much reason not to include it in the list, although you could mark it as optional if you like.
On Wed, 9 May 2012, Dan Smith wrote:
Weird. I don't have python-suds installed, yet Chirp seems to work just fine. What part of the code depends on python-suds?
Well, it doesn't depend on it, in the strict sense of the word.
The radioreference driver uses it, but gracefully handles the case where it's missing. Since it's available on debian, there's not much reason not to include it in the list, although you could mark it as optional if you like.
Now mentioning python-suds as an optional package.
# HG changeset patch # User David Griffith dave@661.org # Date 1336594142 25200 # Node ID ef3839880347f6591ce04101a7e73c3f805c4c24 # Parent 24cb2e48098df646010797cdd3e4664f6b6513c5 New INSTALL and README files
diff -r 24cb2e48098d -r ef3839880347 INSTALL --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/INSTALL Wed May 09 13:09:02 2012 -0700 @@ -0,0 +1,45 @@ +This file describes the installation of Chirp without package management +on Linux and other Unix-like operating systems. This sort of thing may +be your only choice because 1) a package has not yet been made for your +OS or distribution, 2) the packaged version is obsolete, or 3) you want +to try a daily build. + + +For Debian, Ubuntu, and related systems, the following packages are required: +python +python-gtk2 +python-libxml2 +python-libxslt1 +python-serial +python-suds (optional) +python-support + +For Redhat, Fedora, CentOS and related systems, the following packages +are required: (This list is incomplete. Please submit corrections.) +python +pygtk2 +libxml2-python +python-libxslt + + +Once these packages are installed, you can run Chirp directly from the +distribution directory by typing "./chirpw". If you want to install it +properly, type this: + + sudo python setup.py install --record files.txt + +This will install the package and create a list of files that were +added to your system. If you want to deinstall Chirp, type this: + + sudo xargs -0 rm -rf < files.txt + +This will cause rm(1) to take its list of arguments from the file named +"files.txt" and remove those files from the system. If you forgot to +create "files.txt", you can simply reinstall the way it is shown here +and continue on your way. + +Note: This will not uninstall directories created by the installation of +Chirp. Presence of these empty directories shouldn't be a problem, but +if they are, it's easy to go through the files.txt file, identify them, +and remove them. + diff -r 24cb2e48098d -r ef3839880347 README --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/README Wed May 09 13:09:02 2012 -0700 @@ -0,0 +1,16 @@ +Chirp is a free, open-source, multiplatform tool for programming your +amateur radio. It supports a large number of manufacturers and models, +as well as provides a way to interface with multiple data sources and +formats. + +Complete documentation may be found at the Chirp website at +http://chirp.danplanet.com/projects/chirp + +For a list of radios supported by Chirp, type the following command: + + python share/make_supported.py > radios.html + +This will generate an HTML file containing a rundown of all the +currently supported radios and a matrix of what features are supported +for which radio. +
# HG changeset patch # User David Griffith dave@661.org # Date 1336594142 25200 # Node ID ef3839880347f6591ce04101a7e73c3f805c4c24 # Parent 24cb2e48098df646010797cdd3e4664f6b6513c5 New INSTALL and README files
Applied. In the future, please put the bug number in the commit log, not just the email. I added it for you this time.
Thanks!
Okay, here's an updated patch. README.support is eliminated and README has instructions to run "python share/make_supported.py > radios.html".
Looks okay to me. Thanks for making those changes. I'll wait for Tom to ack since he had comments in this thread.
For what it's worth: the rpmdist utilities have complained all along with something like "standard files README and INSTALL are missing from the build". It only gets listed as a warning and does not prevent the generation of an rpm package. This patch should make the utility happy!
Mike, N0SO
participants (4)
-
Dan Smith -
David Griffith -
Mike Heitmann -
Tom Hayward