git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jay Soffian" <jaysoffian@gmail.com>
To: "James B. Byrne" <byrnejb@harte-lyne.ca>
Cc: git@vger.kernel.org
Subject: Re: GiT and CentOS 5.2
Date: Tue, 8 Jul 2008 14:51:17 -0400	[thread overview]
Message-ID: <76718490807081151w7c06bfb5kd0ddfe8e2729dbb5@mail.gmail.com> (raw)
In-Reply-To: <49523.216.185.71.22.1215539200.squirrel@webmail.harte-lyne.ca>

On Tue, Jul 8, 2008 at 1:46 PM, James B. Byrne <byrnejb@harte-lyne.ca> wrote:
> OS = CentOS-5.2
> perl = 5.8.8
>
> I get git from the yum repository at kernel.org.  Up until the most recent
> update I had no problems.  Now I am getting these dependency errors:
>
> Error: Missing Dependency: libcurl.so.4 is needed by package git
> Error: Missing Dependency: perl(:MODULE_COMPAT_5.10.0) is needed by
> package perl-Git
> Error: Missing Dependency: libc.so.6(GLIBC_2.7) is needed by package git
> Error: Missing Dependency: libexpat.so.1 is needed by package git
> Error: Missing Dependency: libcrypto.so.7 is needed by package git
>
>
> Are these dependencies actually meaningful?  By that I mean, are there
> features used in the latest release of GiT that depend upon features of
> GLIBC 2.7 that are not part of glibc-2.5?  Similarly, are there features
> of curl used in the latest git that are not present or work differently in
> curl 7.15.2?  Ditto for OpenSSL and libxpat.
>
> I would like to stay current with git but I cannot if these dependencies
> are actually required.

Junio switched to FC9 for building the git RPMs on kernel.org recently.

Probably the best thing to do if you want a CentOS 5.x RPM is to grab
the source tgz and build the RPM yourself. :-(

There are quite a few build-time dependencies, but those are easy to
take care of with yum.

j.

  parent reply	other threads:[~2008-07-08 18:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-08 17:46 GiT and CentOS 5.2 James B. Byrne
2008-07-08 18:37 ` Mike Hommey
2008-07-08 18:51 ` Jay Soffian [this message]
2008-07-08 19:23 ` Junio C Hamano
2008-07-09 13:25 ` David Voit
2008-07-10 14:32   ` Jeffrey Ollie

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=76718490807081151w7c06bfb5kd0ddfe8e2729dbb5@mail.gmail.com \
    --to=jaysoffian@gmail.com \
    --cc=byrnejb@harte-lyne.ca \
    --cc=git@vger.kernel.org \
    /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).