Date: Tue, 26 Feb 2013 05:09:45 -0800 From: Colin Percival <cperciva@freebsd.org> To: gecko@FreeBSD.org, Ports Management Team <portmgr@freebsd.org> Subject: request: limit patch file names to 100 characters Message-ID: <512CB419.6010705@freebsd.org>
next in thread | raw e-mail | index | archive | help
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? Portmgr, can we have a policy of "no file names over 100 characters"? 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?512CB419.6010705>