Re: Node.js and it's future in debian
On Thu, May 03, 2012 at 02:26:33PM -0400, Patrick Ouellette wrote:
> One of the considerable costs involves the number of systems in place in
> the ham community that are not easily physically accessible should the
> upgrade/change break the system. These systems may be on mountain tops,
> high buildings, or other high structures with significant challenges
> to accessing the locations. These systems may be (usually are) part
> of emergency communications plans and are relied on to help in the
> event of a disaster.
Should the outcome be that the node package renames the binary, and should you
(or whoever does the work) manage to do it wrong, to end up in the scenario you
describe; the machines would only be affected upon upgrade. So some form of
access to the machine would be required to create the problem, be it physical
or remote. The same access should be used to fix the problem.
An experienced ham operator could, at the point where they initiate the
upgrade, symlink /usr/sbin/node -> /usr/sbin/<new node name>, if they are
confident that *they* will never need to install the node.js package. Or
perhaps it could be handled by pre/postinst scripts, as you proposed for nodejs
in another message.