From: Igor Munkin <imun@tarantool.org>
To: "Alexander V. Tikhonov" <avtikhon@tarantool.org>
Cc: tarantool-patches@dev.tarantool.org
Subject: Re: [Tarantool-patches] [PATCH v2 4/5] static build: added build subdirectory cleanup
Date: Wed, 18 Dec 2019 18:34:54 +0300 [thread overview]
Message-ID: <20191218153454.GU1214@tarantool.org> (raw)
In-Reply-To: <444449da1110ff892195a9d5c4176f344f3b5260.1575976611.git.avtikhon@tarantool.org>
Sasha,
Thanks for the patch! I left two comments below, please consider them.
On 10.12.19, Alexander V. Tikhonov wrote:
> Added 'build' directory removement to avoid of old configuration
> at build/curl which is used for curl building.
The commit message looks a bit complex. I rewrote it a little, as the
following:
| Added the command for 'build' directory cleanup. It purges all
| artefacts produced for curl build, including the old configuration in
| build/curl.
Feel free to adjust the commit message in your own way.
> ---
> Dockerfile.staticbuild | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/Dockerfile.staticbuild b/Dockerfile.staticbuild
> index 66342fa4e..0424179a2 100644
> --- a/Dockerfile.staticbuild
> +++ b/Dockerfile.staticbuild
> @@ -72,7 +72,8 @@ RUN set -x && \
>
> RUN set -x && \
> find . -name 'CMakeFiles' -type d -exec rm -rf {} + && \
> - find . -name 'CMakeCache.txt' -type f -delete
> + find . -name 'CMakeCache.txt' -type f -delete && \
Please drop a comment about the build directory source, since it's not
created (or even mentioned) within Docker file.
> + rm -rf build
>
> RUN pip install -r /tarantool/test-run/requirements.txt
>
> --
> 2.17.1
>
--
Best regards,
IM
next prev parent reply other threads:[~2019-12-18 15:37 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-10 11:21 [Tarantool-patches] [PATCH v2 0/5] Improved the static build based on Dockerfile Alexander V. Tikhonov
2019-12-10 11:21 ` [Tarantool-patches] [PATCH v2 1/5] static build: speedup build Alexander V. Tikhonov
2019-12-18 12:21 ` Igor Munkin
2019-12-19 9:26 ` Alexander Tikhonov
2020-04-01 9:56 ` Sergey Bronnikov
2019-12-10 11:21 ` [Tarantool-patches] [PATCH v2 2/5] static build: remove unneeded LD_LIBRARY_PATH Alexander V. Tikhonov
2019-12-18 12:49 ` Igor Munkin
2019-12-19 9:27 ` Alexander Tikhonov
2020-04-01 9:57 ` Sergey Bronnikov
2019-12-10 11:21 ` [Tarantool-patches] [PATCH v2 3/5] static build: cleanup Dockerfile Alexander V. Tikhonov
2019-12-18 15:01 ` Igor Munkin
2019-12-19 9:28 ` Alexander Tikhonov
2020-04-01 9:54 ` Sergey Bronnikov
2019-12-10 11:21 ` [Tarantool-patches] [PATCH v2 4/5] static build: added build subdirectory cleanup Alexander V. Tikhonov
2019-12-18 15:34 ` Igor Munkin [this message]
2019-12-19 9:28 ` Alexander Tikhonov
2020-04-01 9:54 ` Sergey Bronnikov
2019-12-10 11:21 ` [Tarantool-patches] [PATCH v2 5/5] static build: resolve issues with sourceforge.net Alexander V. Tikhonov
2019-12-18 15:55 ` Igor Munkin
2019-12-19 9:34 ` Alexander Tikhonov
2020-04-01 9:53 ` Sergey Bronnikov
2020-04-01 10:18 ` Alexander Tikhonov
2019-12-18 16:01 ` [Tarantool-patches] [PATCH v2 0/5] Improved the static build based on Dockerfile Igor Munkin
2019-12-19 9:29 ` Alexander Tikhonov
2020-04-02 10:35 ` Kirill Yukhin
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=20191218153454.GU1214@tarantool.org \
--to=imun@tarantool.org \
--cc=avtikhon@tarantool.org \
--cc=tarantool-patches@dev.tarantool.org \
--subject='Re: [Tarantool-patches] [PATCH v2 4/5] static build: added build subdirectory cleanup' \
/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