From: Jakub Narebski <jnareb@gmail.com>
To: "James B. Byrne" <byrnejb@harte-lyne.ca>
Cc: git@vger.kernel.org
Subject: Re: [Fwd: Re: GiT and CentOS 5.2]
Date: Tue, 08 Jul 2008 12:12:48 -0700 (PDT) [thread overview]
Message-ID: <m3prpodwb9.fsf@localhost.localdomain> (raw)
In-Reply-To: <50493.216.185.71.22.1215543081.squirrel@webmail.harte-lyne.ca>
"James B. Byrne" <byrnejb@harte-lyne.ca> writes:
> On Tue, July 8, 2008 14:37, Mike Hommey wrote:
> >
> > This only means the rpms in the yum repository at kernel.org were built
> > on a system more recent than yours, and that run-time dependencies (as
> > opposed to build dependencies) require some libraries to be newer than
> > what your system provides.
>
> I understand the meaning of the error messages. What I am asking is
> whether or not any of these dependencies is substantive. If they are then
> I am stuck at the immediately previous release of Git. If not then I have
> the option to either build from source or force an rpm update. If I force
> then I can no long use yum but at least I have the applicate managed by
> rpm. If I build from source then I lose that as well.
>
> So, my question still remains: are these dependencies only artifacts of
> the build environment or do they supply actual features that the latest
> release of Git depends upon and which are not available in the earlier
> version of the software?
They are artifact of the build environment (which picks up the
libraries that they are here); till 1.5.6.1 I have compiled git
and used git succesfully on Fedora Core 4 based dostribution
(Aurox 11.1).
I am now compiling[1] 1.5.6.2, and so far don't have any problems
(now it is at building documentation; it would be nice to be
able to use pre-build documentation from SRPM).
[1] $ rpmbuild --rebuild git-1.5.6.2-1.fc9.src.rpm
--
Jakub Narebski
Poland
ShadeHawk on #git
prev parent reply other threads:[~2008-07-08 19:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-08 18:51 [Fwd: Re: GiT and CentOS 5.2] James B. Byrne
2008-07-08 18:58 ` Jay Soffian
2008-07-08 19:15 ` James B. Byrne
2008-07-08 19:12 ` Jakub Narebski [this message]
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=m3prpodwb9.fsf@localhost.localdomain \
--to=jnareb@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 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.