[Pkg-javascript-devel] Bug#940511: Bug#940511: yarnpkg: Package symlink yarn -> yarnpkg

[Simon Bernard]

Hi all, is there any news on this one ? I mean is this will be fixed on 
current stable version of debian or maybe the next one ?

About popcon score, I think it could have another bias as lot of tooling 
using yarn search a yarn binary and not yarnpkg.  For example vue-cli 
doesn't detect yarn with the debian package because of that. So we could 
imagine that some users could remove this package or don't use it and 
find another way to install yarn.  (Even if a simpler workaround exists 
: ln -s /usr/bin/yarnpkg /usr/bin/yarn)

On Tue, 26 May 2020 20:04:22 +0200 Paolo Greppi <paolo.greppi at libpf.com> 
wrote:
 > See below ...
 >
 > On Wed, 20 May 2020 18:08:29 +0200 =?UTF-8?Q?Ma=C3=ABl_Nison?= 
<mael.nison at datadoghq.com> wrote:
 > > Hi, I'm Maël, Yarn's lead maintainer.
 > >
 > > While cmdtest has a popcon score higher than the yarn package, it's 
mostly
 > > because Yarn isn't traditionally installed using the Debian 
package. For
 > > historical reasons the 1.x branch always updated it, but in general our
 > > users install Yarn using it's "competitor", npm. The npm numbers give a
 > > very different picture: Yarn is downloaded 6.1m times per month.
 > >
 > > There are currently talks to, potentially, ship symlinks for the 
three main
 > > package managers along with Node (npm, which is already there, 
along with
 > > Yarn and maybe pnpm). These plans aren't concrete yet, but a few people
 > > think it's worth studying. In any case, the decision is expected to be
 > > taken for Node 15, which will happen this year. To the extent 
possible, I
 > > think it could be wise (and very appreciated!) to consider renaming the
 > > `yarn` binary from `cmdtest` before it risks becoming an actual 
problem.
 > >
 > > As a last note, I pinged Lars Wirzenius (who I think was the original
 > > cmdtest maintainer?), back in March '19. He mentioned having recently
 > > retired, but seemed fairly supportive of the idea ("I've now 
discussed the
 > > name of our testing tool with its other developer and we will 
likely change
 > > the name of our program during the Debian buster+1 development cycle").
 > >
 > > Maël
 >
 > Hi Maël,
 >
 > thanks for the feedback and for your Debian contribution.
 >
 > I've added here the info on the bug that has to be addressed by the 
cmdtest
 > maintainer (if he agrees) for us to be able to fix this one.
 >
 > I'll also ping him.
 >
 > Paolo
 >
 >