Re: cpio command not found

From: David Symonds <dsymonds@gmail.com>
Date: Oct 31, 2007, 14:00 UTC
Message-ID: <ee77f5c20710310700jf5e4aa4waede0da924d38adc@mail.gmail.com>
In-Reply-To: <18216.35066.259686.376571@lisa.zopyra.com>

On 11/1/07, Bill Lear <rael@zopyra.com> wrote:

Show 20 quoted lines

> On Wednesday, October 31, 2007 at 14:30:39 (+0100) Karl Hasselström writes:
> >On 2007-10-31 06:51:30 -0600, Bill Lear wrote:
> >
> >> I don't remember this dependence from earlier versions of git. I
> >> have been running git 1.4.xx on this machine for a while...
> >
> >When you clone with -l, git uses cpio to hardlink to the original
> >repository. What has changed is that -l is now used by default when
> >cloning a repository that's accessed via the file system (as opposed
> >to over some network protocol).
> >
> >To work around this, specify the repository location with file://, and
> >git won't try to hardlink (and hence won't try to use cpio).
>
> Hmm, thanks for the workaround, but I don't altogether like leaving
> things like this.
>
> If the system does not have cpio, I think the build of git should
> complain and fail, or it should activate code that treats any
> repository accessed over the file system as it would file://.

Something like this could be done at run-time instead. You might install cpio, but shouldn't require a rebuild of git just to use it.

Dave.