Re: [gentoo-dev] rfc: why are we still distributing the portage tree via rsync?

[Matt Turner]

On Tue, Jul 3, 2018 at 12:36 PM Rich Freeman <rich0@g.o> wrote:
>
> On Tue, Jul 3, 2018 at 12:22 PM Matt Turner <mattst88@g.o> wrote:
> >
> > On Tue, Jul 3, 2018 at 11:38 AM Rich Freeman <rich0@g.o> wrote:
> > > 4.  by default git tends to accumulate history, which can eat up disk
> > > space.  I imagine this could be automatically trimmed if users wanted,
> > > though during syncing it would at least need to store all the commits
> > > between the last fetched and next-fetched, and that means fetching
> > > things that might have been subsequently removed/changed
> >
> > This is why I have not switched to git. I have /usr/portage on a
> > separate 1GB partition (with distfiles and packages stored elsewhere).
> > The ebuild tree is 600MB with rsync and cannot fit on the partition
> > with git.
> >
>
> git clone https://github.com/gentoo-mirror/gentoo.git . --depth 1
> ...
> du -sh .
> 662M    .
>
> So, with a shallow clone it seems comparable.
>
> The issue is getting git to constantly trim, probably along the lines of:
> https://stackoverflow.com/a/34829535

Exactly. I'm not sure git can automatically trim out history on git
pull and I'm even less sure it would be able to do it without
temporarily exceeding 1GB of storage.