permissions are set to root during install phase despite destroot permissions

[jameskyle@…]

This behavior only appears in 1.8, it works as expected in 1.7.1. It appears the install phase is changing file and directory ownership from that specified and assigned in the destroot.

For example:

sudo port destroot backuppc
ls -ld work/destroot/${destroot}${prefix}/var/backups
drwxrwx---  7 backuppc  backuppc  272 Jul 30 17:08 work/destroot/${destroot}${prefix}/var/backups

And after install:

ls -ld ${prefix}/var/backups
drwxrwx---  7 root  backuppc  272 Jul 30 17:09 ${prefix}/var/backups }}}

[jmr@…]

May be helped by r54706 (was a little chown-happy before).

[jameskyle@…]

updated to trunk. it's better, the sub directories are getting proper permissions. But the top level one I create is still root:admin after install phasse.

ls -ld ${destroot}${prefix}/var/wwwbackup
drwxrwx---  6 backuppc  backuppc  204 Aug  3 11:00 ${destroot}${prefix}/var/wwwbackup

% ls -ld ../../../mports/var/wwwbackup 
drwxr-xr-x  6 root  admin  204 Aug  3 11:07 ../../../mports/var/wwwbackup

[jmr@…]

I can't reproduce on latest trunk, with a simple test port that creates nested directories in ${prefix}/var owned by me. Are you sure the top level dir wasn't already present?

[jmr@…]

It's been a fortnight; assuming the aforementioned revision fixed this.