Linux HAM/Amateur Radio development
 help / color / mirror / Atom feed
From: Nate Bargmann <n0nb@n0nb.us>
To: debian-hams@lists.debian.org, linux-hams@vger.kernel.org
Subject: Re: AX25 and related software's future in Debian
Date: Wed, 23 May 2012 15:38:35 -0500	[thread overview]
Message-ID: <20120523203835.GH4945@n0nb.us> (raw)
In-Reply-To: <201205231215.27327.wjl@icecavern.net>

* On 2012 23 May 13:16 -0500, Wesley J. Landaker wrote:
> On Thursday, May 03, 2012 19:32:00 Patrick Ouellette wrote:

> > 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.

Long ago I did experiment with the Linux AX.25 stack.  I have long lived
in an area with no packet radio activity so I do not currently use the
ax25 packages.  I like that they are available quite simply via apt and
friends.

I have read the threads that Patrick references and I think the proposed
solution is wrong headed for a few reasons.  Firstly, the 'node' package
has been in Debian for quite a number of releases and now some new
upstream comes along with a conflicting command name.  That there is a
naming conflict is not the issue, but how should it be resolved.  IMO,
node.js upstream should have been a bit more careful with their choice
of name (I'll admit that I have next to zero knowledge of javascript and
how the name 'node' fits into that but as a packet op long ago, 'node'
in the AX.25 context makes perfect sense), but beyond that, doesn't the
length of time that the ax25 upstream has used 'node' without issue not
count for anything?  For anyone to argue with a straight face that the
ax25 packager and upstream must somehow be accountable for this mess
seems to me preposterous.

Assuming the Debian package is forced to rename the 'node' command to
anything else, Debian will be the odd distribution out as far as hams
are concerned.  Will Ubuntu blindly follow suit?  Will any other
distribution?  To hold both packages culpable for the illinformed choice
of one in the name of "fairness" is silly.  As already mentioned, anyone
trying to similarly force a name change of Emacs, Linux, or any other
popular package would be laughed off the mailing list.  And just what
will the Debian decision makers do when ax25 upstream continues to use
the 'node' command name as before?

I can tell you that as a maintainer and contributor to an upstream
project that if I were told by a single distribution that I'd need to
change any of the command names because some upstart decided to use the
same names I would laugh.  Laugh long and hard.  Of course downstream
packagers can do as they like but our releases are staying put.  I
encourage ax25 upstream to do likewise.

Disclaimer, all of my systems run either Debian or a Ubuntu derivative.

> 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.

I've opined plenty on that topic elsewhere.  Today I shall pass.

73, de Nate >>

-- 

"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."

Ham radio, Linux, bikes, and more: http://www.n0nb.us

  reply	other threads:[~2012-05-23 20:38 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
2012-05-23 20:38   ` Nate Bargmann [this message]
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=20120523203835.GH4945@n0nb.us \
    --to=n0nb@n0nb.us \
    --cc=debian-hams@lists.debian.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox