From: | Matt Turner <mattst88@g.o> | ||
---|---|---|---|
To: | gentoo development <gentoo-dev@l.g.o> | ||
Subject: | Re: [gentoo-dev] rfc: why are we still distributing the portage tree via rsync? | ||
Date: | Tue, 03 Jul 2018 16:22:03 | ||
Message-Id: | CAEdQ38HGB=tie35NmJAtF+JGOJJHvvsrkMqb=zL6VPbRwZ2zKg@mail.gmail.com | ||
In Reply to: | Re: [gentoo-dev] rfc: why are we still distributing the portage tree via rsync? by Rich Freeman |
1 | On Tue, Jul 3, 2018 at 11:38 AM Rich Freeman <rich0@g.o> wrote: |
2 | > 4. by default git tends to accumulate history, which can eat up disk |
3 | > space. I imagine this could be automatically trimmed if users wanted, |
4 | > though during syncing it would at least need to store all the commits |
5 | > between the last fetched and next-fetched, and that means fetching |
6 | > things that might have been subsequently removed/changed |
7 | |
8 | This is why I have not switched to git. I have /usr/portage on a |
9 | separate 1GB partition (with distfiles and packages stored elsewhere). |
10 | The ebuild tree is 600MB with rsync and cannot fit on the partition |
11 | with git. |
12 | |
13 | I'd be happy to switch if the space requirements were similar. |
Subject | Author |
---|---|
Re: [gentoo-dev] rfc: why are we still distributing the portage tree via rsync? | Matthias Maier <tamiko@g.o> |
Re: [gentoo-dev] rfc: why are we still distributing the portage tree via rsync? | Rich Freeman <rich0@g.o> |
Re: [gentoo-dev] rfc: why are we still distributing the portage tree via rsync? | grozin@g.o |
[gentoo-dev] Re: rfc: why are we still distributing the portage tree via rsync? | Martin Vaeth <martin@×××××.de> |