From: Jakub Narebski <jnareb@gmail.com>
To: Matthieu Moy <Matthieu.Moy@imag.fr>
Cc: Johan Herland <johan@herland.net>,
git@vger.kernel.org, David Symonds <dsymonds@gmail.com>,
Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH 3/3] The "curl" executable is no longer required
Date: Sun, 15 Jun 2008 15:33:09 +0200 [thread overview]
Message-ID: <200806151533.11742.jnareb@gmail.com> (raw)
In-Reply-To: <vpqej6ylx99.fsf@bauges.imag.fr>
Matthieu Moy wrote:
> Johan Herland <johan@herland.net> writes:
>> On Sunday 15 June 2008, Jakub Narebski wrote:
>>
>>> It is not necessary to enumerate simple library dependencies, as
>>> rpmbuild _detects_ those dependencies during building binary RPMS.
>
> Good to know, and that seems to be a valid argument ("seems to"
> because of my lack of knowledge of rpm, not lack of trust ;-) ).
>
>>> Besides it worked without libcurl in Requires, so it should
>>> continue to work without it, isn't it?
>
> It used to have a dependency on curl, which itself requires libcurl,
> so the dependency was implicit.
>
>> Someone with more RPM knowledge will have to determine which is
>> right.
>
> +1
Or simply remove 'curl' from 'Requires:' header, and check if rpmbuild
would pick up libcurl dependency, and if resulting RPM has libcurl as
requirement.
Fragment of "make rpm" output (word wrapped for better readibility):
[...]
Provides: git-core = 1.5.6.rc3.198.g368e0.dirty-1
Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1
rpmlib(PartialHardlinkSets) <= 4.0.4-1
rpmlib(PayloadFilesHavePrefix) <= 4.0-1
rpmlib(VersionedDependencies) <= 3.0.3-1
Requires: /bin/sh /usr/bin/perl expat less
libc.so.6 libc.so.6(GLIBC_2.0) libc.so.6(GLIBC_2.1) libc.so.6(GLIBC_2.1.1) libc.so.6(GLIBC_2.1.3)
libc.so.6(GLIBC_2.2) libc.so.6(GLIBC_2.2.3) libc.so.6(GLIBC_2.3) libc.so.6(GLIBC_2.3.4)
libcrypto.so.5 libcurl.so.3 libexpat.so.0 libz.so.1
openssh-clients
perl >= 0:5.006 perl(Getopt::Long) perl(Git) perl(lib)
perl(strict) perl(warnings)
perl-Git = 1.5.6.rc3.198.g368e0.dirty-1
rsync zlib >= 1.2
Obsoletes: git-core <= 1.5.4.2 git-p4
[...]
$ rpm -q --requires -p git-1.5.6.rc3.198.g368e0.dirty-1.i386.rpm
/bin/sh
/usr/bin/perl
expat
less
libc.so.6
[...]
libcrypto.so.5
libcurl.so.3
libexpat.so.0
libz.so.1
[...]
As you can see rpmbuild picks up dependency on libcurl.
>From what I remember using automatically picked depndencies is
preferred solution, even if I cannot find it in "Maximum RPM" book.
HTH
--
Jakub Narebski
Poland
next prev parent reply other threads:[~2008-06-15 13:34 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
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 [this message]
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=200806151533.11742.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=Matthieu.Moy@imag.fr \
--cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.