Too bad, we're not talking about manual usage here but also projects likely have build scripts or something. Using aliases is IMO a no-go.
I see presently 2 other packages providing `yarn` executable:
$ sudo dnf whatprovides /usr/bin/yarn [sudo] password for avalon: Last metadata expiration check: 1:37:54 ago on Mon May 21 10:56:24 2018. cmdtest-0.30-1.fc27.noarch : Black-box testing for Unix command line
tools
Repo : fedora Matched from: Filename : /usr/bin/yarn
hadoop-yarn-2.7.3-6.fc27.noarch : Apache Hadoop YARN Repo : fedora Matched from: Filename : /usr/bin/yarn
IMO we should provide some alternatives mechanism so that `yarn` is whatever the user wants. We can't ask upstream packages to change to Fedora specific binary names. Or we can but we will be ignored.
If we don't handle `yarn` better, then users would likely just install `yarn` globally with `npm` and the distro package will not be used. Thus the exercise to maintain it would be mostly worthless.
Neal Gompa wrote on 05/21/18 12:03:
On Mon, May 21, 2018 at 4:35 AM Aleksandar Kostadinov akostadi@redhat.com wrote:
This is really nice! We may think about adding `yarn` support to nodejs openshift buider [1] then.
Presently it is hardcoded to `npm` [2]. But we can add some variable and use yarn when it is set. Like what they did in this blog [3][4].
Please use the "yarnpkg" binary rather than "yarn" binary. Due to conflicts in the repository, "/usr/bin/yarn" is "/usr/bin/nodejs-yarn". But "/usr/bin/yarnpkg" has been preserved from upstream, so that should work.