Charles Curley - Software Engineer, Writer

Fedora Gpsdrive RPMs

I've started building RPMs for Fedora Core 7 from the current CVS source for gpsdrive. I build them every few days, as the fancy takes me. These are Strictly Experimental. You are responsible for finishing the installation, e.g. by setting up the database.

They are signed with my public key, which is available on the index page of this web site, or on key servers everywhere. Or get it like so:

rpm --import http://charlescurley.com/ccurley.asc

There is No Warranty; you are on your own; we're from the government and we're here to help you; don't call us, we'll call you; etc., etc. Support, if any, is via the gpsdrive mailing list. I will not answer questions about these RPMs except on that list.

The status is as follows:

Binary

I have not tested at all. I've had good results in the past, but these are the first RPMs I've built since December, so I consider them untested.

Debug

Completely untested.

Source

Completely untested.

48004871963f52ce609b9f9868ca3a33 gpsdrive-2.10svn1484-1.i386.rpm 00cefa5681628c465c5e4b21fc074f6b gpsdrive-2.10svn1484-1.src.rpm 13e4047c53dce88390554393efaa8dbf gpsdrive-debuginfo-2.10svn1484-1.i386.rpm

43aaae7000744dcb6b42bf8123e531c64b5819d5 gpsdrive-2.10svn1484-1.i386.rpm e0f7c7500442762b51f99ac6a4e3aac5d0662ff8 gpsdrive-2.10svn1484-1.src.rpm 9651b0e819a3ce3c74e991117db356604dfa9427 gpsdrive-debuginfo-2.10svn1484-1.i386.rpm

To ensure that you got a good download, validate the files against the checksums above. The easiest way to do this is to pull in the sha1sum or md5sum files (or both), and run the appropriate program against it:

sha1sum -c sha1sums

or/and

md5sum -c md5sums

Fedora Gpsdrive RPMs

Using the Things