Tarantool development patches archive
 help / color / mirror / Atom feed
From: Vladislav Shpilevoy <v.shpilevoy@tarantool.org>
To: Yaroslav Dynnikov <yaroslav.dynnikov@tarantool.org>,
	lvasiliev <lvasiliev@tarantool.org>
Cc: tarantool-patches@dev.tarantool.org
Subject: Re: [Tarantool-patches] [PATCH v3 0/2] Adapt luarocks for tarantoolctl
Date: Sun, 12 Apr 2020 21:52:50 +0200	[thread overview]
Message-ID: <20b61d2a-8b5a-f97e-23a4-6c6ae3cb6a17@tarantool.org> (raw)
In-Reply-To: <CAK0MaD1dPvgwz8mwO=QcbxnWg79GscTehb_f5_ujVrvA9eef2w@mail.gmail.com>

> 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.

  reply	other threads:[~2020-04-12 19:52 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-09  6:33 Leonid Vasiliev
2020-04-09  6:33 ` [Tarantool-patches] [PATCH v3 1/2] Add the chdir option for make Leonid Vasiliev
2020-04-09  6:33 ` [Tarantool-patches] [PATCH v3 2/2] Delete flags which can't be used with tarantoolctl rocks Leonid Vasiliev
2020-04-13 11:59   ` lvasiliev
2020-04-13 12:16     ` Yaroslav Dynnikov
2020-04-10  0:00 ` [Tarantool-patches] [PATCH v3 0/2] Adapt luarocks for tarantoolctl Vladislav Shpilevoy
2020-04-10  8:41   ` lvasiliev
2020-04-10 17:02   ` Yaroslav Dynnikov
2020-04-10 18:37     ` lvasiliev
2020-04-11 14:23     ` Vladislav Shpilevoy
2020-04-12 17:25       ` lvasiliev
2020-04-12 18:30         ` Yaroslav Dynnikov
2020-04-12 19:52           ` Vladislav Shpilevoy [this message]
2020-04-13  7:44           ` lvasiliev
2020-04-13 11:07 ` lvasiliev

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20b61d2a-8b5a-f97e-23a4-6c6ae3cb6a17@tarantool.org \
    --to=v.shpilevoy@tarantool.org \
    --cc=lvasiliev@tarantool.org \
    --cc=tarantool-patches@dev.tarantool.org \
    --cc=yaroslav.dynnikov@tarantool.org \
    --subject='Re: [Tarantool-patches] [PATCH v3 0/2] Adapt luarocks for tarantoolctl' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox