2016-02-27 13:16 GMT+01:00 Jonas Smedegaard <d...@jones.dk>:
> Quoting Jérémy Lal (2016-02-27 10:25:44)
> > no newcomers ever find out that nodejs-legacy provides the
> > nodejs -> node
> > symlink.
> > It is probably because the name of this package is badly chosen.
> > Any suggestion ?
> > nodejs-symlink-node ?
> I find the package name descriptive: It accurately frames the _main_
> trait of that package which is that it is for _legacy_ use only.
"legacy" can only be understood if one knows that it refers to the fact it
For example it could refer to an old version, so users not aware just don't
look into it.
This leads to users manually adding the symlink, often in the wrong place
(like in /usr/bin),
which then leads to more problems.
could be just the right hint.
It would be easy to transition to it, since no other packages depend on it.
> What we might instead consider improve is short/long description fields.
Indeed, and also make sure it is correctly explained in both nodejs/npm