[Fwd: Re: GiT and CentOS 5.2]

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?

-- 
***          E-Mail is NOT a SECURE channel          ***
James B. Byrne                mailto:ByrneJB@Harte-Lyne.ca
Harte & Lyne Limited          http://www.harte-lyne.ca
9 Brockley Drive              vox: +1 905 561 1241
Hamilton, Ontario             fax: +1 905 561 0757
Canada  L8E 3C3


-- 
***          E-Mail is NOT a SECURE channel          ***
James B. Byrne                mailto:ByrneJB@Harte-Lyne.ca
Harte & Lyne Limited          http://www.harte-lyne.ca
9 Brockley Drive              vox: +1 905 561 1241
Hamilton, Ontario             fax: +1 905 561 0757
Canada  L8E 3C3

On Tue, Jul 8, 2008 at 2:51 PM, James B. Byrne [off-list ref] wrote:

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?

You could of course answer this yourself. Download the latest RPM, rpm
--nodeps or rpm2cpio it and see if it works.

But from the looks of it, the git binary links against libraries not
on your system and it will not work.

j.

"James B. Byrne" [off-list ref] writes:

On Tue, July 8, 2008 14:37, Mike Hommey wrote: 

quoted

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

On Tue, July 8, 2008 14:58, Jay Soffian wrote:

You could of course answer this yourself. Download the latest RPM, rpm
--nodeps or rpm2cpio it and see if it works.

But from the looks of it, the git binary links against libraries not
on your system and it will not work.

Yes, it appears so.  Having just converted our projects from subversion to
git I am reluctant to beat my brains out trying to maintain yet another
moving target that is, in the end, only a support tool. The most recent
GiT source builds without complaint on my development system so the
dependencies are purely build environment artifacts and are not
substantive.  This change to the rpm build platform is unfortunate for me
since I now lose a very convenient update process and have to choose
between rebuilding at each release or stabilizing at 1.5.6.1.

Nonetheless, I will no doubt live through this... Sigh.


-- 
***          E-Mail is NOT a SECURE channel          ***
James B. Byrne                mailto:ByrneJB@Harte-Lyne.ca
Harte & Lyne Limited          http://www.harte-lyne.ca
9 Brockley Drive              vox: +1 905 561 1241
Hamilton, Ontario             fax: +1 905 561 0757
Canada  L8E 3C3