Bug#940511: [Pkg-javascript-devel] Bug#940511: Our mutual interest in /usr/bin/yarn
On Mon, 21 Nov 2022 09:39:31 +0100 "Yadd" wrote: I don't think that "Provides: yarn" is a good thing here since "/usr/bin/yarn" isn't provided by yarnpkg. "Provides: node-yarn" seems enough here and without any consequences. As a compromise, can we have a debconf prompt to notify users about this conflict and to run sudo ln -s /usr/bin/yarnpkg /usr/bin/yarn if they want to use yarn command. Automating this via a postinst may be a good idea too, but not sure if that is allowed by policy. May be we can ask for an exception since this is a special case. This way people who want to use yarn command has a way to do it easily. Prompting users is a bad idea in general if we can have good defaults, but we don't have much options left here. OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#940511: [Pkg-javascript-devel] Bug#940511: Our mutual interest in /usr/bin/yarn
Le Dimanche, Novembre 20, 2022 12:34 CET, Geert Stappers a écrit: > On Wed, Nov 09, 2022 at 09:21:15PM +0100, Geert Stappers wrote: > > Hello JavasScript people, > > Hello Python people, > > > :-) > > > We both want to use /usr/bin/yarn for a program, > > unfortunately different programs. > > > > What about agreeing on a disagreement? > > > > So binary packages cmdtest and yarnpkg conflict each other? > > After rethinking that: It might work for a large part, > but it realy blocks the people who want to install both packages. > > The plan is now to patch the debian yarnpkg package > so it has clearly visible that it provides `yarn`. > > > Groeten > Geert Stappers Hi, I don't think that "Provides: yarn" is a good thing here since "/usr/bin/yarn" isn't provided by yarnpkg. "Provides: node-yarn" seems enough here and without any consequences. Cheers, Yadd
