[ thread split off into separate topic - Mod. ]
Is it normal, that some ports directories (e.g /usr/ports/www/firefox36) have permissions which does not allow user (from wheel group) to check out e.g distfiles or Makefiles or simply... get there? I am asking you because yesterday I saw a little, red X on some directories. One of them is firefox36 dir (latest firefox-3.6.15,1). It is strange, because a couple of days ago, I was able to enter there and check all files. Now I can not, even via console [1]. There is several directories with similar right access in whole ports tree - most in the cad category.
What I did over the last few days? Update ports via portsnap utility, clean distfiles from /usr/ports/distfiles/ directory with portmaster. That's all. I never had a such situation, where I can not enter to the some application directory in the ports tree because of acces permissions. Or maybe I never put my attention on it? Or, finally, maybe it is because of what phoenix wrote?; "The first month or so after a FreeBSD release sees *a lot* of churn in the ports tree." But my problem relates to a computer running FreeBSD 8.1 Release. I am so confused.
Best regards!
[CMD=""][1] $ cd /usr/ports/www/firefox36[/CMD]
Is it normal, that some ports directories (e.g /usr/ports/www/firefox36) have permissions which does not allow user (from wheel group) to check out e.g distfiles or Makefiles or simply... get there? I am asking you because yesterday I saw a little, red X on some directories. One of them is firefox36 dir (latest firefox-3.6.15,1). It is strange, because a couple of days ago, I was able to enter there and check all files. Now I can not, even via console [1]. There is several directories with similar right access in whole ports tree - most in the cad category.
What I did over the last few days? Update ports via portsnap utility, clean distfiles from /usr/ports/distfiles/ directory with portmaster. That's all. I never had a such situation, where I can not enter to the some application directory in the ports tree because of acces permissions. Or maybe I never put my attention on it? Or, finally, maybe it is because of what phoenix wrote?; "The first month or so after a FreeBSD release sees *a lot* of churn in the ports tree." But my problem relates to a computer running FreeBSD 8.1 Release. I am so confused.
Best regards!
[CMD=""][1] $ cd /usr/ports/www/firefox36[/CMD]
Code:
/usr/ports/www/firefox36: Permission denied.