git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Paxton <kpaxton@paxdesigns.com>
To: Dennis Kaarsemaker <dennis@kaarsemaker.net>
Cc: git@vger.kernel.org
Subject: Re: Dependencies required for offline installation
Date: Tue, 5 Jul 2016 14:06:14 -0400	[thread overview]
Message-ID: <CAOkrQryazf=38eUMjcZzByjk=OVNfFGpFKnp5zpyML7yDKhW=A@mail.gmail.com> (raw)
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:
> 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.

  reply	other threads:[~2016-07-05 18:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-05 11:45 Dependencies required for offline installation Kevin Paxton
2016-07-05 17:53 ` Dennis Kaarsemaker
2016-07-05 18:06   ` Kevin Paxton [this message]
2016-07-05 19:53     ` Dennis Kaarsemaker
2016-07-05 22:45       ` brian m. carlson
2016-07-05 18:09 ` Konstantin Khomoutov

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='CAOkrQryazf=38eUMjcZzByjk=OVNfFGpFKnp5zpyML7yDKhW=A@mail.gmail.com' \
    --to=kpaxton@paxdesigns.com \
    --cc=dennis@kaarsemaker.net \
    --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).