request: limit patch file names to 100 characters

[Martin Wilke]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

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?
> 
> 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


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (FreeBSD)

iEYEARECAAYFAlEsxA0ACgkQdLJIhLHm/OmwTACeNe3Ibz9qiM0ZovRjiXEdTVFj
JEwAn05tk1JZtsxEDo+gzTm/ZQfESuEN
=EjyN
-----END PGP SIGNATURE-----