Look I mean in any other context for a git repository sync-depth=0 would be the obvious choice, why have a version control system if you're limiting the version control. It was added to gentoo so that developers could work on their own branches of the git repo whilst still having it actually work with portage. And then the next logical application is making your own /usr/local/portage not suck. Using git as the main sync instead of rsync is something that's come about way later, and really is fairly niche, compared to what the git capability in portage was originally designed for.
So the default being for git to act like git, instead of git to act like an alternative to rsync, makes perfect sense in that context. On Thu, 14 Oct 2021 at 18:22, Peter Humphrey <pe...@prh.myzen.co.uk> wrote: > > On Thursday, 14 October 2021 03:50:59 BST Grant Edwards wrote: > > On 2021-10-13, Rich Freeman <ri...@gentoo.org> wrote: > > > On Wed, Oct 13, 2021 at 2:50 PM Grant Edwards > <grant.b.edwa...@gmail.com> wrote: > > >> Is there some reason it should default > > >> to doing unlimited depth fetch operations? > > > > > > If all you want is a repo, no reason to set the depth higher. > > > > Then a default of 1 seems like the obvious "right" answer. > > Unfortunately, it defaults to "unlimited" according to > > https://wiki.gentoo.org/wiki//etc/portage/repos.conf > > > > sync-depth > > > > Specifies sync depth to use for DVCS repositories. If set to 0, > > the depth is unlimited. Defaults to 0. > > > > > If you want to see the history then you'll want it all. > > > > Apparently, that's the default. Without any sync-depth setting the > > fetch was stalling and then timing out after 60s. With sync-depth=1, > > the fetch completed in about 1s. > > I have it set to 8 here, for no reason I can remember. Is there a disadvantage > in that? > > -- > Regards, > Peter. > > > >
