Date: Sat, 03 Sep 2011 05:11:07 -0700 From: perryh@pluto.rain.com To: avg@freebsd.org Cc: freebsd-arch@freebsd.org Subject: Re: Official git export Message-ID: <4e62195b.cdaZfeF621ojSqVQ%perryh@pluto.rain.com> In-Reply-To: <4E5F4807.6070206@FreeBSD.org> References: <CAMBSHm8uX45k0M4on=5Cpw_CKoddA=4oJSNXpH7dGPt=Vy2HOw@mail.gmail.com> <alpine.BSF.2.00.1108261000040.48200@fledge.watson.org> <slrnj5lc58.jd1.vadim_nuclight@kernblitz.nuclight.avtf.net> <4e5ba9c3.bzHIw1KEy8R2QcK7%perryh@pluto.rain.com> <3420B331-C697-468A-80BA-B31C33804710@freebsd.org> <4e5c5b5f.moT7dLemOuteQJ5T%perryh@pluto.rain.com> <4E5C364D.7070904@freebsd.org> <CAHM0Q_Mq3YEEpB6uNymjtd=WCQuTR6gd=71EsLxJf5J0ygyjiw@mail.gmail.com> <20110830201357.GB58638@acme.spoerlein.net> <4e5e458a.Un%2BVK0itRgItvxbf%perryh@pluto.rain.com> <20110831081815.GN2493@over-yonder.net> <4e5f2e26.6PQ5d6F3eauFfAcH%perryh@pluto.rain.com> <4E5F12B6.3090307@FreeBSD.org> <4e5fa001.BTxOKlcJfp7aZ2KE%perryh@pluto.rain.com> <4E5F4807.6070206@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Andriy Gapon <avg@freebsd.org> wrote: > ... keeping local history is of course not necessary, but when > you need to do some serious history analysis it comes extremely > convenient. In the area where one is working, certainly, but I don't expect to need the commit history of the contrib tree while working on UFS or gmirror. > few hundred MB is nothing for a development environment. A few hundred MB of disk space is nothing. Having to _download_ a few hundred MB of source code, that one already has, is _not_ "nothing" unless one has a rather large pipe. I'm not the first to raise this point: http://lists.freebsd.org/pipermail/freebsd-arch/2011-August/011595.html http://lists.freebsd.org/pipermail/freebsd-arch/2011-August/011605.html One way to mitigate this would be to provide the ability to download and install VCS metadata (back-deltas, commit comments, etc.) for particular files and directories "as needed". If that level of granularity is problematic, just splitting the metadata into 5 groups would help: group contents size * infrastructure all files directly in /usr/src; and 66 MB subdirs etc, include, lib, libexec, release, rescue, share, tools. contrib /usr/src/contrib 232 MB crypto /usr/src/{crypto,kerberos5,secure} 40 MB kernel /usr/src/sys 143 MB other /usr/src/{bin,cddl,games,gnu, 50 MB sbin,usr.bin,usr.sbin} * size of /usr/src/... reported by "du -s" in 8.1. This is the size of the code, not including any VCS metadata, but it seems likely to give a reasonable idea of the relative metadata sizes (i.e. the size of a group's metadata will be -- very roughly -- proportional to the size of its code). For that matter, FreeBSD could provide the VCS metadata corresponding to each release as a separate ISO, so those who need it can obtain and install it. Those for whom large downloads are a problem could buy it on CD. > ... doing some non-trivial FreeBSD development myself ... Unless you're considerably older than you look in that Flickr photo from about a year ago (in Kiev), I was doing non-trivial OS development before you finished middle school :)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4e62195b.cdaZfeF621ojSqVQ%perryh>