From: Leonid Vasiliev <lvasiliev@tarantool.org> To: v.shpilevoy@tarantool.org Cc: tarantool-patches@dev.tarantool.org Subject: [Tarantool-patches] [PATCH v2 0/3] Adapt luarocks for tarantoolctl Date: Sun, 5 Apr 2020 17:50:06 +0300 [thread overview] Message-ID: <cover.1586096636.git.lvasiliev@tarantool.org> (raw) https://github.com/tarantool/tarantool/issues/4629 https://github.com/tarantool/luarocks/tree/lvasiliev/gh-4629-add-chdir-to-make See corresponding patch for tarantoolctl (https://github.com/tarantool/tarantool/tree/lvasiliev/gh-4629-forward-flags) Motivation: Imperfect integretion of the Luarocks to tarantoolctl (malfunctioning flags, disabled commands, invalid help) Was done: Whitelist in tarantoolctl has been changed to blacklist in luarocks Help has been updated Option chdir has been moved from tarantoolctl to luarocks @ChangeLog - see a comment in tarantool Leonid Vasiliev (3): Add the chdir option for make Add a black list for tarantoolctl rocks options Adapt luarocks help for tarantoolctl rocks src/luarocks/cmd/config.lua | 18 +++++++++--------- src/luarocks/cmd/help.lua | 10 +++------- src/luarocks/cmd/make.lua | 15 ++++++++++++--- src/luarocks/cmd/new_version.lua | 2 +- src/luarocks/cmd/purge.lua | 2 +- src/luarocks/util.lua | 15 +++++++++++++++ 6 files changed, 41 insertions(+), 21 deletions(-) -- 2.7.4
next reply other threads:[~2020-04-05 14:50 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-04-05 14:50 Leonid Vasiliev [this message] 2020-04-05 14:50 ` [Tarantool-patches] [PATCH v2 1/3] Add the chdir option for make Leonid Vasiliev 2020-04-05 18:40 ` Vladislav Shpilevoy 2020-04-05 14:50 ` [Tarantool-patches] [PATCH v2 2/3] Add a black list for tarantoolctl rocks options Leonid Vasiliev 2020-04-05 14:50 ` [Tarantool-patches] [PATCH v2 3/3] Adapt luarocks help for tarantoolctl rocks Leonid Vasiliev
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=cover.1586096636.git.lvasiliev@tarantool.org \ --to=lvasiliev@tarantool.org \ --cc=tarantool-patches@dev.tarantool.org \ --cc=v.shpilevoy@tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH v2 0/3] 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