git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Dependencies required for offline installation

From
KPKevin Paxton <kpaxton@paxdesigns.com>
Date
Jul 5, 2016, 18:06 UTC
Message-ID
<CAOkrQryazf=38eUMjcZzByjk=OVNfFGpFKnp5zpyML7yDKhW=A@mail.gmail.com>
In-Reply-To
<1467741182.14863.6.camel@kaarsemaker.net>
Thank you for the response.
I apologize. RHEL 6.5, not 5.5.

Would the same version be applicable to 6.5 as well as the dependencies that you mentioned?

On Tue, Jul 5, 2016 at 1:53 PM, Dennis Kaarsemaker <dennis@kaarsemaker.net> wrote:

Show 24 quoted lines
> On di, 2016-07-05 at 07:45 -0400, Kevin Paxton wrote:
>> Hi,
>>
>> I’m looking to install git on a separate network that is running
>> Redhat 5.5.
>
> That's ancient and unsupported. If you insist on using rhel 5, at least
> do 5.11 so you get the security updates.
>
>> I need to know what is the list of packages that I need to
>> download to be able to install git-all? I plan on using git-svn to
>> migrate an existing svn repo over to git as well. Svn version we have
>> installed is 1.9.3.
>
> There are rpms for git 1.8 in EPEL. git-all is probably overkill, but
> you'll need at least git, perl-Git, perl-Git-SVN and perl-Error.
>
>> Does the tarball contain all dependencies already? Should I go that
>> route? Or should I try and find all the rpm's required?
>
> The source tarball of git contains no dependencies. Also be aware that
> building git from source requires even more dependencies.
>
> D.
Previous: Dennis KaarsemakerNext: Dennis Kaarsemaker
Message 3 of 6 in “Dependencies required for offline installation”
  1. Kevin PaxtonJul 5, 2016
  2. Dennis KaarsemakerJul 5, 2016
  3. Kevin PaxtonJul 5, 2016
  4. Dennis KaarsemakerJul 5, 2016
  5. brian m. carlsonJul 5, 2016
  6. Konstantin KhomoutovJul 5, 2016

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.