From owner-freebsd-gecko@FreeBSD.ORG Tue Feb 26 14:38:17 2013 Return-Path: Delivered-To: gecko@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 5D355DC0; Tue, 26 Feb 2013 14:38:17 +0000 (UTC) (envelope-from miwi@bsdhash.org) Received: from bsdhash.org (bsdhash.org [94.23.250.27]) by mx1.freebsd.org (Postfix) with ESMTP id C784C842; Tue, 26 Feb 2013 14:38:16 +0000 (UTC) Received: by bsdhash.org (Postfix, from userid 1002) id 50BCC51137; Tue, 26 Feb 2013 22:38:15 +0800 (MYT) Date: Tue, 26 Feb 2013 22:38:15 +0800 From: Martin Wilke To: Colin Percival Subject: Re: request: limit patch file names to 100 characters Message-ID: <20130226143815.GD2419@bsdhash.org> References: <512CB419.6010705@freebsd.org> <20130226141750.GC2419@bsdhash.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; x-action=pgp-signed In-Reply-To: <20130226141750.GC2419@bsdhash.org> X-Editor: Vim http://www.vim.org/ X-Mailer: Mutt http://www.mutt.org/ User-Agent: Mutt/1.5.21 (2010-09-15) Cc: gecko@FreeBSD.org, Ports Management Team X-BeenThere: freebsd-gecko@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Martin Wilke List-Id: Gecko Rendering Engine issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Feb 2013 14:38:17 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, Feb 26, 2013 at 10:17:50PM +0800, Martin Wilke wrote: > On Tue, Feb 26, 2013 at 05:09:45AM -0800, Colin Percival wrote: > > Hi all, > > > > I just uncovered a slight glitch in portsnap while doing my latest testing: > > It has problems with the www/seamonkey port due to the patch file > > "patch-mozilla-media-webrtc-trunk-src-modules-audio_device-main-source-linux-latebindingsymboltable_linux.cc". > > > > More precisely, because this file name is 107 characters long, it can't fit > > into a ustar header, so bsdtar switches to the pax extended format, which > > contains additional information like the access time and inode #, which of > > course changes from run to run of the portsnap build code. As a result, this > > one port is identified as "changing" every single time the build runs. > > > > Gecko folks, would you mind renaming this to something shorter? Done! > > > > Portmgr, can we have a policy of "no file names over 100 characters"? > > > > > I think that should be fine. > > > > I can work around this by hacking up the copy of tar on the portsnap buildbox > > to exclude the changing fields, but I'd prefer to minimize the hurdles facing > > anyone else who wants to use the portsnap build code. > > > > > -- > > Colin Percival > > Security Officer Emeritus, FreeBSD | The power to serve > > Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid > > > > -- > +-----------------oOO--(_)--OOo-------------------------+ > With best Regards, > Martin Wilke (miwi_(at)_FreeBSD.org) > > > Mess with the Best, Die like the Rest > > > - -- +-----------------oOO--(_)--OOo-------------------------+ With best Regards, Martin Wilke (miwi_(at)_FreeBSD.org) Mess with the Best, Die like the Rest -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlEsyNYACgkQdLJIhLHm/OlnUACeJ6xS09zX3rj1+5KpbCoBsyMQ 7q4AnifBw7Sz3MSvauqxIgt2Rqu9SOvt =mwDU -----END PGP SIGNATURE-----