From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp59.i.mail.ru (smtp59.i.mail.ru [217.69.128.39]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dev.tarantool.org (Postfix) with ESMTPS id D13D64696C3 for ; Sun, 12 Apr 2020 22:52:54 +0300 (MSK) References: <865fb768-3c90-ec8e-96cf-7d7598a9f6e0@tarantool.org> <711c06ec-7953-fcb0-f0cd-a1b68a37e8ae@tarantool.org> From: Vladislav Shpilevoy Message-ID: <20b61d2a-8b5a-f97e-23a4-6c6ae3cb6a17@tarantool.org> Date: Sun, 12 Apr 2020 21:52:50 +0200 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="utf-8" Content-Language: en-US Content-Transfer-Encoding: 8bit Subject: Re: [Tarantool-patches] [PATCH v3 0/2] Adapt luarocks for tarantoolctl List-Id: Tarantool development patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Yaroslav Dynnikov , lvasiliev Cc: tarantool-patches@dev.tarantool.org > Please, notice that command-line help refers to `tarantoolctl help > path`, but > > 1. It should be `tarantoolctl rocks help` (I guess there are many of >    such places) Fix of 'help' sections appeared to be a task far from trivial. There are tens of places, where 'luarocks' should be replaced with 'tarantoolctl rocks'. That would make the fork even more far from the upstream, and would make luarocks not self-sufficient. Because now it depends only on 'tarantool', but will depend on 'tarantoolctl' too. See other emails on the 'help' subject in this thread. I don't know what to do with that really. My best proposal was to pass an option to luarocks init in tarantoolctl with a program name to use, and replace it where necessary. But this is also very intrusive.