From owner-freebsd-current@freebsd.org Thu Dec 29 10:44:36 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 5A6E1C961BE for ; Thu, 29 Dec 2016 10:44:36 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C9E811852 for ; Thu, 29 Dec 2016 10:44:35 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from thor.walstatt.dynvpn.de ([85.178.51.182]) by mail.gmx.com (mrgmx003 [212.227.17.190]) with ESMTPSA (Nemesis) id 0LqRKT-1d0Inb3ZGz-00e12u; Thu, 29 Dec 2016 11:44:27 +0100 Date: Thu, 29 Dec 2016 11:44:20 +0100 From: "O. Hartmann" To: blubee blubeeme Cc: freebsd-current@freebsd.org Subject: Re: A question about updating src & ports Message-ID: <20161229114408.4dfdbb8e@thor.walstatt.dynvpn.de> In-Reply-To: References: Organization: WALSTATT User-Agent: OutScare 3.1415926 X-Operating-System: ImNotAnOperatingSystem 3.141592527 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; boundary="Sig_/ut1ZX_HkfxGTeXPSZenB1dU"; protocol="application/pgp-signature" X-Provags-ID: V03:K0:VFrWao+j66nkR5m+AhEfejC1U/+9dnH2w67QhmH4qyNAJrlYqJ3 FiigI8CRTKCnvvudmh2kbd+qLmjVAq+wUZ37KNMhjxEEI13LuvF5OlAIysI2WXqLUwsFLef rWX8w9+F+hJHpp3+B/suAN3NEKJMKSo7Ca2OcjyWkVhRB/vwTA/HhmGKwkeznIcmS+wO2Dq Dch0FfaXwAJwEso1B3yZg== X-UI-Out-Filterresults: notjunk:1;V01:K0:ov/kUzLieAo=:VQaA7TA1+KPMAIvwQJ8IB5 /+PmOrqIkI1SWriu+GNgI/mO5GdyxuW6B2DR4D1iqWbjofshUzcPSKHNfqUUxCLUSPQD3lkMh jYeUy+7V8HJuCOv8Z6DVVonBsAiU/G6nIRUbrpWuno+Vnvg6lM4QHH9BPuPwnvdi5k4fS9dF2 3rnHA+e3m4N05jXiJATDDo3rXpYNLI12MktDkLILr6WDp4JLRW7APrL7TAAwPTdvO5N3YEHhi 9E+jUj/speWD5PC6bqMWcS0Dpi0JqKnwUTBbDf9qwm7MQKPRQYPJbNtI5ay2uF6liv7vPs9K6 0F8May1DnaoRYOQTviNEsMkF5EMhQRifbLSNWtMB7gmdPIhsQI6CN+A31L/f3DjrP08iCR8QI 0H/VTvMCmVS3KBAbMkMl4uJsVFlN2bLJtjH22KvvzReEM7AwdFK9TYAkaRRUCjY4uZ+1lIAjp ln4WtfvuCcuI4RoVAC/x8dgN8nbIHKBXINehx1LwjWz4PH+CrHT4fMfI8IWUmUnY/fQ37Ci0S kpW81MtXoMxEu+SOTVKudUE0UmIF6BZgruZoaqcAgM4VOuSY/FOX8nxyS+BjULnM0Yv7u1Lb+ rj1baKo/uOarv6HVASdkHfhTBe1kQrQ3SgdSvlHcFNmx+brQK8mqU9+ApZd3P7mDJDH5SSDFI LjonpyYdpGXhBEKK+Lci5BPvBibj9jEOnxXZFFNAWIpXRgQl4uIxBudCTRGexkQyT7A3+cTkC KpGgvskwqVzTpwwVxV/w7VBwUNDbeInb3zjujai/bbU5mjkRTyTimPKU5bk= 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: Thu, 29 Dec 2016 10:44:36 -0000 --Sig_/ut1ZX_HkfxGTeXPSZenB1dU Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Am Thu, 29 Dec 2016 18:11:38 +0800 blubee blubeeme schrieb: > Howdy >=20 > I went through the process of building world for the first time, that was > interesting but I got it. svn clean up prior object files, build world, > kernel, etc. >=20 > Okay that part is fine >=20 > I have a question about keeping ports up to date, in the past I did > portsnap fetch update to update the ports but since I totally deleted all > the ports and used svn checkout to get the latest ports. >=20 > Can I mix portsnap fetch update or should I just continue to use svn upda= te > /usr/ports >=20 > Best, > Owen Well, from my own experience I left the path of "portsnap" and stay with svn alon= e. 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 - i= t 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 nu= mber of files. Therefore, I switched to svn. Well, svn itself is pumping up /usr/ports/.svn where it keeps all logs. Dep= ending on the frequency of updates it grows. I do the same for /usr/src and by the time o= f 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 sometimes the filesystem is full. I avoid ZFS on build machines and use par= titions for /usr/src, /usr/obj and sibblings which saved my ass several times for n= ow. ZFS is a memory hog, on /usr/ports (which is on ZFS in mz scenario, the exclusion ..= .), a "svn update" can take up to 8 minutes on a 16GB, freshly rebooted box with a 3,4= Ghz XEON IvyBridge CPU and a ZFS RAIDZ with 4 HDDs and SSD for ZIL and L2ARC.=20 On the other hand - I once tried to mix portsnap and svn and apart from any= theory it worked a while and then it failed. That might be due to non-synchronisation= between portsnap serving facilities and subversion repositories - which I would exp= ect not to be in sync withing femto seconds. So it might be wise to saty with one specifi= c method - I decided myself to keep it with svn. Just my experience, Kind regards, Oliver =20 --=20 O. Hartmann Ich widerspreche der Nutzung oder =C3=9Cbermittlung meiner Daten f=C3=BCr Werbezwecke oder f=C3=BCr die Markt- oder Meinungsforschung (=C2=A7 28 Abs.= 4 BDSG). --Sig_/ut1ZX_HkfxGTeXPSZenB1dU Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCWGTpBAAKCRDS528fyFhY lJD2Af9qQT0HO++SSYqGi0OuQxo3UWzS1VY/71Yx9ANGpuGVac/OcUMh4jnLcgj8 CnePpshRGJb7/+I4J3slshL7LogLAgCS4LLEf73aafUw5a2IxUn+fzVIkdlorwQ1 NMWF7rFbq57kdCQNs4xWrtiqHgGs7+HccTYzbVuUq/YHjm8vMuKc =kt5U -----END PGP SIGNATURE----- --Sig_/ut1ZX_HkfxGTeXPSZenB1dU--