request: limit patch file names to 100 characters

Colin Percival cperciva at
Tue Feb 26 13:10:34 UTC 2013

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

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 | | Online backups for the truly paranoid

More information about the freebsd-gecko mailing list