From: Ray Wells <vk2tv@exemail.com.au>
To: "Curt, WE7U" <curt.we7u@gmail.com>
Cc: Gordon JC Pearce <gordonjcp@gjcp.net>,
David Ranch <linux-hams@trinnet.net>,
Linux Hams <linux-hams@vger.kernel.org>
Subject: Re: Packet Radio Crawlers for Linux?
Date: Tue, 21 Jun 2011 07:29:33 +1000 [thread overview]
Message-ID: <4DFFBBBD.7010702@exemail.com.au> (raw)
In-Reply-To: <alpine.LNX.2.00.1106200902180.10051@DadsBox.we7u.net>
On 21/06/11 02:05, Curt, WE7U wrote:
> On Mon, 20 Jun 2011, Ray Wells wrote:
>
>> Xastir is probably "newer" than almost any other aprs application,
>> being that it is constantly being developed and supported by a very
>> active mailing list. It works perfectly.
>
> Many people see the Xastir versions that come out in official Linux
> distributions and assume they are the newest available. Some
> distributions are a bit slow at including newer packages for apps.
> Sometimes two years or more before they get around to it. From that
> viewpoint, everything looks pretty old.
>
> Curt... One of those Xastir guys.
One of the good guys!!
Maybe I've been using Debian based systems for too long - about 18 years
- so I know the packages are often (usually, always?) not the latest.
I do get a bit crabby when someone makes a sweeping statement - it
doesn't work - without qualifying the statement.
Ray vk2tv
next prev parent reply other threads:[~2011-06-20 21:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-20 1:09 Packet Radio Crawlers for Linux? David Ranch
2011-06-20 6:45 ` Gordon JC Pearce
2011-06-20 7:39 ` Ray Wells
2011-06-20 16:05 ` Curt, WE7U
2011-06-20 16:50 ` Gordon JC Pearce
2011-06-20 21:29 ` Ray Wells [this message]
2011-06-20 21:53 ` Bob Nielsen
2011-06-20 17:35 ` David Ranch
2011-06-20 19:08 ` Thomas Osterried
2011-06-20 22:21 ` David Ranch
2011-06-20 23:41 ` Douglas Cole
2011-06-21 0:59 ` David Ranch
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4DFFBBBD.7010702@exemail.com.au \
--to=vk2tv@exemail.com.au \
--cc=curt.we7u@gmail.com \
--cc=gordonjcp@gjcp.net \
--cc=linux-hams@trinnet.net \
--cc=linux-hams@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.