From: "David Symonds" <dsymonds@gmail.com>
To: "Johan Herland" <johan@herland.net>
Cc: "Junio C Hamano" <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH 3/3] The "curl" executable is no longer required
Date: Sun, 15 Jun 2008 20:52:43 +1000 [thread overview]
Message-ID: <ee77f5c20806150352n6ccf00e9w8083a17d8c5c2326@mail.gmail.com> (raw)
In-Reply-To: <200806151216.01886.johan@herland.net>
On Sun, Jun 15, 2008 at 8:16 PM, Johan Herland <johan@herland.net> wrote:
> diff --git a/git.spec.in b/git.spec.in
> index 97a26be..d946bb1 100644
> --- a/git.spec.in
> +++ b/git.spec.in
> @@ -12,7 +12,7 @@ BuildRequires: zlib-devel >= 1.2, openssl-devel,
> curl-devel, expat-devel, gettex
> BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)
>
> Requires: perl-Git = %{version}-%{release}
> -Requires: zlib >= 1.2, rsync, curl, less, openssh-clients, expat
> +Requires: zlib >= 1.2, rsync, less, openssh-clients, expat
> Provides: git-core = %{version}-%{release}
> Obsoletes: git-core <= 1.5.4.2
> Obsoletes: git-p4
Shouldn't libcurl still be listed as a requirement? Or is it statically linked?
Dave.
next prev parent reply other threads:[~2008-06-15 10:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-12 7:20 Cleaning up INSTALL before 1.5.6 Johan Herland
2008-06-15 10:13 ` [PATCH 1/3] cpio is no longer used by git-clone Johan Herland
2008-06-15 10:14 ` [PATCH 2/3] Consistency: Use "libcurl" instead of "cURL library" and "curl" Johan Herland
2008-06-15 10:16 ` [PATCH 3/3] The "curl" executable is no longer required Johan Herland
2008-06-15 10:52 ` David Symonds [this message]
2008-06-15 10:55 ` Johan Herland
2008-06-15 10:59 ` David Symonds
2008-06-15 11:23 ` Matthieu Moy
2008-06-15 11:40 ` [PATCH 3/3 v2] " Johan Herland
2008-06-15 11:42 ` [PATCH 3/3] " Jakub Narebski
2008-06-15 11:47 ` Johan Herland
2008-06-15 12:04 ` Matthieu Moy
2008-06-15 13:33 ` Jakub Narebski
2008-06-15 13:53 ` Johan Herland
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=ee77f5c20806150352n6ccf00e9w8083a17d8c5c2326@mail.gmail.com \
--to=dsymonds@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=johan@herland.net \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).