I created BUILDR-646 for this issue. I believe I could patch this, but don't want to commit to that right this moment as I'm in the middle of a big move after purchasing my first home. If I do manage to break some time free to do it I will though.
On Tue, Jul 17, 2012 at 1:58 PM, Alex Boisvert <alex.boisv...@gmail.com>wrote: > On Tue, Jul 17, 2012 at 9:33 AM, Damian Monogue <demon...@gmail.com> > wrote: > > > I was working with one of our developers today, and he mentioned he'd > > noticed something odd when building his application. We create a tgz file > > at one point during the build process, and then we use that artifact > later > > on to create a solaris .pkg file. But, when running that tgz through > > Builder::Unzip#extract it does not retain permissions. > > > > I went and looked through the docs, and when viewing the source for the > > extract method, I notice that the tgz handler has the following commented > > out, but the zip handler does not: entry.restore_permissions = true . > > > > Sidenote: It's commented but even if it wasn't, it wouldn't work because > the entry itself isn't used to create the file -- we use File#open to > recreate it so it requires an explicit call to set permissions. > > Is this an oversight, or was there some reason for this that I'm not > > seeing? While we can probably use a zip and be fine, we would prefer to > use > > tarballs. > > > > Looks like an oversight to me. Is this something you think you can fix > and send a patch for? If not, I can work on it later this week. > > alex >
