Tarantool development patches archive
 help / color / mirror / Atom feed
From: lvasiliev <lvasiliev@tarantool.org>
To: Oleg Babin <olegrok@tarantool.org>, v.shpilevoy@tarantool.org
Cc: tarantool-patches@dev.tarantool.org
Subject: Re: [Tarantool-patches] [PATCH] rocks: forward options to luarocks
Date: Thu, 2 Apr 2020 11:30:58 +0300	[thread overview]
Message-ID: <bd07aff0-096c-4f6c-0f2c-38ce69db829e@tarantool.org> (raw)
In-Reply-To: <3037d64f-69fe-86ed-e30c-60e1704bfa69@tarantool.org>

Hi, thanks for the feedback.

On 01.04.2020 13:44, Oleg Babin wrote:
> Hi! Thanks for your patch I have several comments.
> 
> On 26/03/2020 01:01, Leonid Vasiliev wrote:
>  > From: Leonid <lvasiliev@tarantool.org>
>  >
>  > https://github.com/tarantool/tarantool/issues/4629
>  > 
> https://github.com/tarantool/tarantool/tree/lvasiliev/gh-4629-forward-flags
>  >
>  > Corresponding thread 
> https://lists.tarantool.org/pipermail/tarantool-patches/2020-March/015143.html 
> 
>  >
>  > @Changelog
> Please put branch, issue and changelog under "---". This should not be a 
> part of commit message.
>  > Chdir has been moved to luarocks.
> 
> It's quite important thing to preserve backward compatibility.
> How it works now:
> ```
> tarantoolctl rocks make --chdir ../tracing
> 
> Warning: variable CFLAGS was not passed in build_variables
> mkdir -p doc
> tracing scm-1 is now installed in 
> /Users/o.babin/Projects/tarantool/.rocks (license: BSD)
> ```
> 
> How it looks on your branch:
> ```
> ./src/tarantool ./extra/dist/tarantoolctl rocks make --chdir ../tracing
> 
> Error: Invalid argument: unknown flag --chdir. See --help.
> ```
> 
> And I don't see any mentions of this option in "rocks --help". May be I 
> do something wrong? But make sure that behaviour of this option was not 
> changed. It's quite important for solutions.
As I understand it, you use luarocks from the system, you need use 
luaroks from the repo (use export LUA_PATH=...).
> 
> ---
> Oleg Babin

  reply	other threads:[~2020-04-02  8:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-25 22:01 Leonid Vasiliev
2020-04-01 10:44 ` Oleg Babin
2020-04-02  8:30   ` lvasiliev [this message]
2020-04-02  8:53     ` Oleg Babin
2020-04-02  9:56 ` lvasiliev
2020-04-02 10:14   ` Oleg Babin
2020-04-04 19:30 ` Vladislav Shpilevoy
2020-04-05 15:01   ` lvasiliev
2020-04-05 18:40     ` Vladislav Shpilevoy
  -- strict thread matches above, loose matches on Subject: below --
2019-11-18 18:26 Leonid

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=bd07aff0-096c-4f6c-0f2c-38ce69db829e@tarantool.org \
    --to=lvasiliev@tarantool.org \
    --cc=olegrok@tarantool.org \
    --cc=tarantool-patches@dev.tarantool.org \
    --cc=v.shpilevoy@tarantool.org \
    --subject='Re: [Tarantool-patches] [PATCH] rocks: forward options to luarocks' \
    /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