From: Johan Herland <hidden> Date: 2016-06-15 22:44:43
AFAICS, there's a couple of things that should be changed in the list of
system requirements:
- cpio is no longer needed due to git-clone now being a builtin
- According to some other thread on this list, curl might no longer be
needed, as all its users are now builtin, and uses libcurl instead.
Have fun! :)
...Johan
--
Johan Herland, [off-list ref]
www.herland.net
@@ -83,9 +83,6 @@ Issues of note: - "perl" and POSIX-compliant shells are needed to use most of the barebone Porcelainish scripts.- - "cpio" is used by git-clone when doing a local (possibly- hardlinked) clone.- - Some platform specific issues are dealt with Makefile rules, but depending on your specific installation, you may not have all the libraries/tools needed, or you may have
@@ -15,8 +15,8 @@ DESCRIPTION Sends missing objects to remote repository, and updates the remote branch.-*NOTE*: This command is temporarily disabled if your cURL-library is older than 7.16, as the combination has been reported+*NOTE*: This command is temporarily disabled if your libcurl+is older than 7.16, as the combination has been reported not to work and sometimes corrupts repository. OPTIONS
@@ -186,7 +186,7 @@ Step 3: setup the client ------------------------ Make sure that you have HTTP support, i.e. your git was built with-curl (version more recent than 7.10). The command 'git http-push' with+libcurl (version more recent than 7.10). The command 'git http-push' with no argument should display a usage message. Then, add the following to your $HOME/.netrc (you can do without, but will be
@@ -13,7 +13,7 @@ all::# Define NO_OPENSSL environment variable if you do not have OpenSSL.# This also implies MOZILLA_SHA1.#-# Define NO_CURL if you do not have curl installed. git-http-pull and+# Define NO_CURL if you do not have libcurl installed. git-http-pull and# git-http-push are not built, and you cannot use http:// and https://# transports.#
@@ -158,7 +158,7 @@ AC_CHECK_LIB([crypto], [SHA1_Init], AC_SUBST(NEEDS_SSL_WITH_CRYPTO) AC_SUBST(NO_OPENSSL) #-# Define NO_CURL if you do not have curl installed. git-http-pull and+# Define NO_CURL if you do not have libcurl installed. git-http-pull and # git-http-push are not built, and you cannot use http:// and https:// # transports. AC_CHECK_LIB([curl], [curl_global_init],
From: Johan Herland <hidden> Date: 2016-06-15 22:44:46
git-clone.sh was the last user of the "curl" executable. Relevant git
commands now use libcurl instead. This should be reflected in the
install requirements.
Signed-off-by: Johan Herland <redacted>
---
I haven't tested the RPM spec change, but it seems fairly straightforward...
INSTALL | 8 ++++----
git.spec.in | 2 +-
2 files changed, 5 insertions(+), 5 deletions(-)
@@ -67,10 +67,10 @@ Issues of note: that come with git (git includes the one from Mozilla, and has its own PowerPC and ARM optimized ones too - see the Makefile).- - "libcurl" and "curl" executable. git-http-fetch and- git-fetch use them. If you do not use http- transfer, you are probably OK if you do not have- them.+ - libcurl library; git-http-fetch and git-fetch use them. You+ might also want the "curl" executable for debugging purposes.+ If you do not use http transfer, you are probably OK if you+ do not have them. - expat library; git-http-push uses it for remote lock management over DAV. Similar to "curl" above, this is optional.
Shouldn't libcurl still be listed as a requirement? Or is it
statically linked?
It is not necessary to enumerate simple library dependencies, as
rpmbuild _detects_ those dependencies during building binary RPMS.
Only unusual requirements (on programs (tools) or on specific version
of library) are needed to be added in Requires header.
This has nothing to do with BuildRequires. Besides it worked without
libcurl in Requires, so it should continue to work without it,
isn't it?
--
Jakub Narebski
Poland
ShadeHawk on #git
Shouldn't libcurl still be listed as a requirement? Or is it
statically linked?
It is not necessary to enumerate simple library dependencies, as
rpmbuild _detects_ those dependencies during building binary RPMS.
Only unusual requirements (on programs (tools) or on specific version
of library) are needed to be added in Requires header.
This has nothing to do with BuildRequires. Besides it worked without
libcurl in Requires, so it should continue to work without it,
isn't it?
Unfortunately I don't know this format at all. There are now two versions of
the patch, one without "Requires: curl", and one where it's replaced
by "Requires: libcurl". Someone with more RPM knowledge will have to
determine which is right.
...Johan
--
Johan Herland, [off-list ref]
www.herland.net