Tarantool development patches archive
 help / color / mirror / Atom feed
From: "Alexander V. Tikhonov" <avtikhon@tarantool.org>
To: Kirill Yukhin <kyukhin@tarantool.org>,
	Sergey Bronnikov <sergeyb@tarantool.org>,
	Alexander Turenko <alexander.turenko@tarantool.org>
Cc: tarantool-patches@dev.tarantool.org
Subject: [Tarantool-patches] [PATCH v1 2/4] build: remove libyaml from rpm/deb dependencies
Date: Thu, 18 Jun 2020 08:36:50 +0300	[thread overview]
Message-ID: <9583c86c694943a5e1d860e8671d39952a4ae66f.1592458150.git.avtikhon@tarantool.org> (raw)
In-Reply-To: <cover.1592458150.git.avtikhon@tarantool.org>
In-Reply-To: <cover.1592458150.git.avtikhon@tarantool.org>

From: Serge Petrenko <sergepetrenko@tarantool.org>

After we started using bundled version of libyaml by default (see commit
47b91e90f2a4e23e70a1a6735af3de203ffd59f4), we can remove it from
building dependencies for RPM and DEB packages.

Closes #4442

Reviewed-by: Alexander Turenko <alexander.turenko@tarantool.org>
(cherry picked from commit 1d4e584a7b5a5570486d7dfa6df82e664f8e0f95)
---
 debian/control     | 3 +--
 rpm/tarantool.spec | 1 -
 2 files changed, 1 insertion(+), 3 deletions(-)

diff --git a/debian/control b/debian/control
index 91d0b0e44..ea2e151fd 100644
--- a/debian/control
+++ b/debian/control
@@ -8,7 +8,6 @@ Build-Depends: cdbs (>= 0.4.100), debhelper (>= 9), dpkg-dev (>= 1.16.1~),
  cmake,
  libreadline-dev,
  libncurses5-dev,
- libyaml-dev,
  libssl-dev,
  libunwind-dev | libunwind8-dev | libunwind7-dev,
  libicu-dev,
@@ -54,7 +53,7 @@ Package: tarantool
 Architecture: i386 amd64 armhf arm64
 Priority: optional
 Depends: ${shlibs:Depends}, ${misc:Depends}, netbase, binutils, libgomp1,
- libyaml-0-2, openssl, tarantool-common (>= 1.7.5.46),
+  openssl, tarantool-common (>= 1.7.5.46),
 # libcurl dependencies (except ones we have already)
  zlib1g
 Replaces: tarantool-lts
diff --git a/rpm/tarantool.spec b/rpm/tarantool.spec
index 4b6ea6f9f..88b1d6b5c 100644
--- a/rpm/tarantool.spec
+++ b/rpm/tarantool.spec
@@ -15,7 +15,6 @@ BuildRequires: gcc-c++ >= 4.5
 BuildRequires: coreutils
 BuildRequires: sed
 BuildRequires: readline-devel
-BuildRequires: libyaml-devel
 BuildRequires: openssl-devel
 BuildRequires: libicu-devel
 #BuildRequires: msgpuck-devel
-- 
2.17.1

  parent reply	other threads:[~2020-06-18  5:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-18  5:36 [Tarantool-patches] [PATCH v1 0/4] Fix app/digest and app/socket on 1.10 Alexander V. Tikhonov
2020-06-18  5:36 ` [Tarantool-patches] [PATCH v1 1/4] build: enable bundled libyaml for all systems Alexander V. Tikhonov
2020-06-18  5:36 ` Alexander V. Tikhonov [this message]
2020-06-18  5:36 ` [Tarantool-patches] [PATCH v1 3/4] Bump libyaml Alexander V. Tikhonov
2020-06-18  5:36 ` [Tarantool-patches] [PATCH v1 4/4] Extend range of printable unicode characters Alexander V. Tikhonov
2020-06-18 10:39 ` [Tarantool-patches] [PATCH v1 0/4] Fix app/digest and app/socket on 1.10 Alexander Turenko
2020-06-22 13:58   ` Alexander V. Tikhonov
2020-06-23 14:08     ` Alexander Turenko
2020-06-26  9:46 ` 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=9583c86c694943a5e1d860e8671d39952a4ae66f.1592458150.git.avtikhon@tarantool.org \
    --to=avtikhon@tarantool.org \
    --cc=alexander.turenko@tarantool.org \
    --cc=kyukhin@tarantool.org \
    --cc=sergeyb@tarantool.org \
    --cc=tarantool-patches@dev.tarantool.org \
    --subject='Re: [Tarantool-patches] [PATCH v1 2/4] build: remove libyaml from rpm/deb dependencies' \
    /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