[Pkg-javascript-devel] Is anyone maintaining (the ham radio tool) node?

[Philipp Kern]

On 2011-11-08, Patrick Ouellette <pat at flying-gecko.net> wrote:
> I hope to avoid any issues with breaking old boxes with the eventual
> resolution of the issue.

I don't know what's wrong with Jonathan Nieder's advise in [0] about helping
users with the conversion automatically.  That's how it's usually done.
He even provided that patch.

Who would refer to the node binary as provided by the ham package node
except for the inetd and the ax25d superservers?  (Serious question.)

Because as we're providing a whole distribution we could adjust the latter's
configuration file and ensure that both packages are upgraded (using Breaks,
for instance).

> The issue is one of following policy.  Debian policy doesn't allow such a 
> "resolution" to this issue. Consensus on which must change, or both must
> change are the only allowed outcomes.

In this case the two packages at least don't ship the same file.  With the
current situation you can coinstall the packages and both parts ham and
nodejs shebangs will keep working.

But then policy talks of "filenames" and I don't know if that refers to files
with a full path or not…  If so, invoking policy as a reason wouldn't help
here.

Kind regards
Philipp Kern

[0] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=614907