On Sat, Apr 06, 2013 at 12:26:14PM -0700, Tai-Lin Chu wrote:
@dave I still cannot find any info regarding why we should not use depth 1. do you mind pasting the link here? thanks.
https://mailman.archlinux.org/pipermail/pacman-dev/2012-March.txt Now curl and grep are your friends...
On Sat, Apr 6, 2013 at 12:15 PM, Dave Reisner <d@falconindy.com> wrote:
On Sat, Apr 6, 2013 at 3:11 PM, Tai-Lin Chu <tailinchu@gmail.com> wrote:
...what are you trying to test?
Probably trying to replicate what makepkg does to show you why cp doesn't work.
mkdir -p /tmp/dumb/ pushd /tmp/dumb/ echo "==> Cloning into a bare repository..." git clone --verbose git://github.com/falconindy/cower.git barerepo echo "==> Creating copy of this repo using cp..." cp -r -a /tmp/dumb/barerepo /tmp/dumb/barecp echo "==> Done" echo "==> Creating copy of this repo using git clone..." git clone --verbose /tmp/dumb/barerepo barerepocopy echo "==> Done"
test this. of course --bare will give you different result...
And this is what makepkg uses so that the base repo takes up less space on disk and the tree doesn't need to be calculated.
ok here is a normal process that i mentioned:
git clone --depth 1 git://github.com/falconindy/cower.git test cp -a -r test test2 // build with test2 rm -rf test2
Please go back and search the pacman-dev list for why we aren't doing this -- it's clear that you posted the suggestion here before doing any amount of investigation into this. You aren't the first to suggest this, and you unfortunately won't be the last.
-- William Giokas | KaiSforza GnuPG Key: 0x73CD09CF Fingerprint: F73F 50EF BBE2 9846 8306 E6B8 6902 06D8 73CD 09CF