On Thu, May 03, 2012 at 04:20:46PM -0400, Patrick Ouellette wrote: > On Thu, May 03, 2012 at 10:11:41PM +0200, Raphael Hertzog wrote: > > > > > You also don't address the issue of a user who installs both packages > > > and now gets varying behavior depending on their $PATH - a result not > > > of a local administrator's action, but of the Debian package's actions. > > > > If node gets renamed to ax25-node, the conflict will disappear, no? > > Not if your backwards compatibility symlink is there.
One could identify the compatibility symlink (vs. a local user created symlink) by another layer of indirection: /usr/sbin/node -> /usr/share/node/compatibity-symlink -> /usr/sbin/<new node name> Then, either node or nodejs could manipulate the symlink without interfering with local customisations. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120504080653.GC5371@debian
