Pascal Jäger writes: > Maybe I’m getting this wrong, but didn’t  we switch to shallow > checkouts for the systems repository? I remember it was a major > outcry on the mailing list. So at least for end users git keeps no > history and our repository history should not impact clone size of a > shallow copy, should it?  > (Try to avoid top-posting if you can, reply after the message you're replying to.) rsync copies of the tree aren't affected by this, nor are full git clones for development. > > > On Donnerstag, Apr. 27, 2023 at 14:54, Michał Górny < > mgorny@gentoo.org> wrote: > On Thu, 2023-04-27 at 09:58 +0200, Florian Schmaus wrote: > > Disk space is cheap. > > > No, it's not. Gentoo supports more hardware than your average PC > with > beefy hard drive and/or possibility of installing one. Let's not > forget > that you need a ::gentoo checkout even on a system running purely > on binary packages. > > Let's not forget that git keeps all history, so every bump of a > Go > package with large Manifest has a permanent negative impact on > clone > size. A few version bumps of Go packages can easily outweigh > complete > history of hundreds of other packages.  > > > Network traffic, while also being cheap, may be more of an > issue. > > > Again, you're making assumption based on living in a > well-developed area > and discriminating against users who have shoddy Internet > connectivity. > > That said, this all was discussed in the past. I really wish you > would > humble down and try to find a solution that would work for > everyone > instead of showing arrogance and lack of concern for users > outside your > "majority" view of Gentoo. > > -- > Best regards, > Michał Górny > >