From owner-freebsd-ports@FreeBSD.ORG  Mon May 20 07:56:47 2013
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: freebsd-ports@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by hub.freebsd.org (Postfix) with ESMTP id 9909023D
 for <freebsd-ports@freebsd.org>; Mon, 20 May 2013 07:56:47 +0000 (UTC)
 (envelope-from poyopoyo@puripuri.plala.or.jp)
Received: from msa01b.plala.or.jp (msa01.plala.or.jp
 [IPv6:2400:7800:0:5010::1])
 by mx1.freebsd.org (Postfix) with ESMTP id 1618C1DF
 for <freebsd-ports@freebsd.org>; Mon, 20 May 2013 07:56:46 +0000 (UTC)
Received: from i125-201-4-220.s02.a026.ap.plala.or.jp ([125.201.4.220])
 by msa01b.plala.or.jp with ESMTP id
 <20130520075637.UCGY10521.msa01b.plala.or.jp@i125-201-4-220.s02.a026.ap.plala.or.jp>;
 Mon, 20 May 2013 16:56:37 +0900
Date: Mon, 20 May 2013 16:56:37 +0900
Message-ID: <8661yedqyy.wl%poyopoyo@puripuri.plala.or.jp>
From: poyopoyo@puripuri.plala.or.jp
To: sindrome <sindrome@gmail.com>
Subject: Re: Why does Samba requires 777 permissions on /tmp
In-Reply-To: <CAFzAeSdgRotc34+eyfVHZBA-QGUCWJ1MZDYw1ysRxEV9MhG2BQ@mail.gmail.com>
References: <CAFzAeSdgRotc34+eyfVHZBA-QGUCWJ1MZDYw1ysRxEV9MhG2BQ@mail.gmail.com>
Mail-Followup-To: sindrome <sindrome@gmail.com>, freebsd-ports@freebsd.org,
 poyopoyo@puripuri.plala.or.jp
User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI/1.14.6 (Maruoka)
 FLIM/1.14.9 (=?ISO-2022-JP-2?B?R29qGyQoRCtXGyhC?=) APEL/10.8 Emacs/24.3
 (amd64-portbld-freebsd10.0) MULE/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
X-VirusScan: Outbound; msa01b; Mon, 20 May 2013 16:56:37 +0900
Cc: freebsd-ports@freebsd.org
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 20 May 2013 07:56:47 -0000

At Sat, 18 May 2013 18:34:47 -0500,
sindrome wrote:
> /usr/local/lib/ruby/site_ruby/1.8/pkgtools/pkgtools.rb:483: warning:
> Insecure world writable dir /tmp in PATH, mode 040777

At Sun, 19 May 2013 23:31:21 -0500,
sindrome wrote:
> /usr/local/lib/ruby/site_ruby/1.8/pkgtools/pkgtools.rb:483: warning:
> Insecure world writable dir /tmp/. in PATH, mode 041777

At Sun, 19 May 2013 21:30:03 +0200,
Simon Wright wrote:
> /usr/local/lib/ruby/site_ruby/1.8/pkgtools/pkgtools.rb:288: warning: 
> Insecure world writable dir /tmp/ in PATH, mode 041777

/tmp
/tmp/.
/tmp/

Interesting three different messages.
It looks like three different entities adds their own value to your PATH.

What you guys should do first is to find who sets stupid PATH for you.
I don't suppose portupgrade does.