From owner-freebsd-current@freebsd.org Sat Dec 31 03:52:19 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 035E1C9863A for ; Sat, 31 Dec 2016 03:52:19 +0000 (UTC) (envelope-from kaduk@mit.edu) Received: from dmz-mailsec-scanner-7.mit.edu (dmz-mailsec-scanner-7.mit.edu [18.7.68.36]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id AB5D51996 for ; Sat, 31 Dec 2016 03:52:18 +0000 (UTC) (envelope-from kaduk@mit.edu) X-AuditID: 12074424-bb7ff70000005087-07-58672a377893 Received: from mailhub-auth-3.mit.edu ( [18.9.21.43]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by (Symantec Messaging Gateway) with SMTP id B3.18.20615.73A27685; Fri, 30 Dec 2016 22:47:03 -0500 (EST) Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) by mailhub-auth-3.mit.edu (8.13.8/8.9.2) with ESMTP id uBV3l3E3003257; Fri, 30 Dec 2016 22:47:03 -0500 Received: from kduck.kaduk.org (24-107-191-124.dhcp.stls.mo.charter.com [24.107.191.124]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id uBV3kx6T013858 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 30 Dec 2016 22:47:02 -0500 Date: Fri, 30 Dec 2016 21:46:59 -0600 From: Benjamin Kaduk To: "O. Hartmann" Cc: blubee blubeeme , freebsd-current@freebsd.org Subject: Re: A question about updating src & ports Message-ID: <20161231034659.GF8460@kduck.kaduk.org> References: <20161229114408.4dfdbb8e@thor.walstatt.dynvpn.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20161229114408.4dfdbb8e@thor.walstatt.dynvpn.de> User-Agent: Mutt/1.6.1 (2016-04-27) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrEIsWRmVeSWpSXmKPExsUixCmqrWuulR5hsGmBmcWcNx+YLJbtW89k sf/eYXYHZo8Zn+azeOycdZfdY9670ywBzFFcNimpOZllqUX6dglcGV3fowpOc1QsuJPUwPia rYuRk0NCwETiUvtlxi5GLg4hgTYmiRt/ZjNBOBsZJfoX/GQEqRISuMok8feXJ4jNIqAqsev2 bWYQm01ARaKh+zKQzcEhIqAlce6QA0iYWcBN4lXvVlYQW1jASOLQ069g5bwCxhKbpvSzQsxv AZq/+gZUQlDi5MwnLBDNWhI3/r1kApnJLCAtsfwfB0iYU8BO4vGl62AzRQWUJRpmPGCewCgw C0n3LCTdsxC6FzAyr2KUTcmt0s1NzMwpTk3WLU5OzMtLLdI118vNLNFLTSndxAgKWnYXlR2M 3T3ehxgFOBiVeHgf3EiLEGJNLCuuzD3EKMnBpCTKa2mZGiHEl5SfUpmRWJwRX1Sak1p8iFGC g1lJhDdHIz1CiDclsbIqtSgfJiXNwaIkznsp0z1CSCA9sSQ1OzW1ILUIJivDwaEkwesB0ihY lJqeWpGWmVOCkGbi4AQZzgM0fDHY8OKCxNzizHSI/ClGRSlxXktNoIQASCKjNA+uF5RUJLL3 17xiFAd6RZhXCKSKB5iQ4LpfAQ1mAhqslpMMMrgkESEl1cBY/c/+YPrcd56N72+eTH+bIcQQ v9Q4Kmt9+L7yOP0Q7ewW3XUc914kT9q7VvflnUSjNs3TuroL9FedmiA1JefXyjS90kMqSQuP /i2euTVkRRKnzm7XgHVifzOTpykefT3fmWvb+4LAj5Kdxv+V58+QvPcvQi1zy9SW7LajzuLu cyQ+ivwI2hWvxFKckWioxVxUnAgAU1okgwUDAAA= X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 31 Dec 2016 03:52:19 -0000 On Thu, Dec 29, 2016 at 11:44:20AM +0100, O. Hartmann wrote: > > from my own experience I left the path of "portsnap" and stay with svn alone. portsnap > tends to "flood" the /var filesystem with a tremendous number of files over time. Each > time you issue "portsnap fetch update", a file appears in /var/portsnap - it could be > that the files appear in /var/db, I can't remember. Deleting them with "rm -rf *" leaves > me then with an error from "rm": the argument line is to long due to the number of files. > Therefore, I switched to svn. > > Well, svn itself is pumping up /usr/ports/.svn where it keeps all logs. Depending on the > frequency of updates it grows. I do the same for /usr/src and by the time of fetching > almost every day several times a day updates, the folder .svn is as large > as /usr/src itself in its pristine state when fetched initially. For > long-haul/long-running systems I'm concerned about the flood of data coming in and 'svn cleanup .' will reduce the size of .svn/ by deleting old copies of pristine files that are no longer needed. -Ben