From: "Wesley J. Landaker" <wjl@icecavern.net>
To: debian-hams@lists.debian.org
Cc: Patrick Ouellette <pat@flying-gecko.net>, linux-hams@vger.kernel.org
Subject: Re: AX25 and related software's future in Debian
Date: Wed, 23 May 2012 12:15:23 -0600 [thread overview]
Message-ID: <201205231215.27327.wjl@icecavern.net> (raw)
In-Reply-To: <20120504013200.GB3489@flying-gecko.net>
[-- Attachment #1: Type: Text/Plain, Size: 1260 bytes --]
On Thursday, May 03, 2012 19:32:00 Patrick Ouellette wrote:
> I come to the lists mentally and physically exhausted from the
> current struggle to defend the ham radio package node in the Debian
> distribution. I also seem to be the only person interested in the
> ax25 software (libax25, ax25-tools, ax25-xtools, and ax25-utils).
> The situation with node has made me wonder why I am even bothering. I
> can compile the ax25 stack for my use, and not have to put up with the
> baggage Debian requires.
>
> The question I have for the lists - is there really any interest in
> having ham radio software, particularly libax25 and the tools/utils in
> Debian? I know if it disappears from Debian it affects all Debian
> derived distros (like Ubuntu for instance).
I do not use any ax25 software at the moment, but I've always had it on my
list of interesting things to try: back when I was younger (I wasn't a ham
at the time) I helped a friend of mine set up packet radio software on his
computer.
About ham radio software in general, I do use a lot of other ham radio
software packaged in Debian. In general I'm surprised that there isn't more
overlap between the ham radio and free/open-source software communities.
- W5OSS
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2012-05-23 18:15 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-04 1:32 AX25 and related software's future in Debian Patrick Ouellette
2012-05-04 1:46 ` Dave Platt
2012-05-04 2:10 ` Patrick Ouellette
2012-05-04 1:53 ` Kamal Mostafa
2012-05-04 2:03 ` Charles Suprin
2012-05-04 2:17 ` Patrick Ouellette
2012-05-04 2:20 ` Alejandro Santos
2012-05-04 5:20 ` Kim, VK5FJ
2012-05-04 14:34 ` Patrick Ouellette
2012-05-04 14:06 ` Dan Smith
2012-05-04 15:14 ` Patrick Ouellette
2012-05-04 15:35 ` Dan Smith
2012-05-04 16:28 ` Steve Kostecke
2012-05-04 16:57 ` Patrick Ouellette
2012-05-04 17:50 ` Bill Vodall
2012-05-04 18:06 ` Patrick Ouellette
2012-05-04 18:32 ` Dan Smith
2012-05-04 18:49 ` Patrick Ouellette
2012-05-04 19:01 ` Dan Smith
2012-05-04 19:31 ` Patrick Ouellette
2012-05-04 22:52 ` Damien Gardner Jnr
[not found] ` <CAPSBm51zYFpfPa0Rqvjemv4KGh-NQfFmFTcW07B8KzpTK_E8bw@mail.gmail.com>
2012-05-05 3:00 ` Kris Kirby
2012-05-05 13:33 ` Thomas Osterried
2012-05-23 18:15 ` Wesley J. Landaker [this message]
2012-05-23 20:38 ` Nate Bargmann
2012-05-23 22:48 ` Damien Gardner Jnr
2012-05-24 12:18 ` C.J. Adams-Collier
2012-05-24 12:33 ` IT1 Stuart Blake Tener, USNR
2012-05-24 23:05 ` Marius Petrescu
2012-05-24 23:29 ` IT1 Stuart Blake Tener, USNR
2012-05-25 0:02 ` Marius Petrescu
2012-05-25 0:04 ` Marius Petrescu
2012-05-25 0:56 ` Bob Nielsen
2012-05-25 1:46 ` Nate Bargmann
[not found] <S1754044Ab2EQTsl/20120517194841Z+66@vger.kernel.org>
2012-05-17 20:03 ` Charles Boling (AD7UF)
2012-05-17 20:25 ` John Goerzen
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=201205231215.27327.wjl@icecavern.net \
--to=wjl@icecavern.net \
--cc=debian-hams@lists.debian.org \
--cc=linux-hams@vger.kernel.org \
--cc=pat@flying-gecko.net \
/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.