From owner-freebsd-ports@FreeBSD.ORG  Sat Dec 15 03:06:19 2007
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: freebsd-ports@freebsd.org
Received: from freefall.freebsd.org (localhost [127.0.0.1])
	by hub.freebsd.org (Postfix) with SMTP id DB28A16A4C7;
	Sat, 15 Dec 2007 03:06:18 +0000 (UTC)
	(envelope-from nork@FreeBSD.org)
Date: Sat, 15 Dec 2007 12:06:18 +0900
From: Norikatsu Shigemura <nork@FreeBSD.org>
To: Stephen Montgomery-Smith <stephen@math.missouri.edu>
Message-Id: <20071215120618.1bf43910.nork@FreeBSD.org>
In-Reply-To: <47632096.8080008@math.missouri.edu>
References: <47630A20.60807@janh.de> <47631447.9090009@u.washington.edu>
	<1197676276.1838.23.camel@ikaros.oook.cz>
	<47632096.8080008@math.missouri.edu>
X-Mailer: Sylpheed 2.4.7 (GTK+ 2.12.1; i386-portbld-freebsd8.0)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: Jan Henrik Sylvester <me@janh.de>,
	Garrett Cooper <youshi10@u.washington.edu>, pav@freebsd.org,
	ports-list freebsd <freebsd-ports@freebsd.org>
Subject: Re: misc/compat5x package installs with weird messages
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/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: Sat, 15 Dec 2007 03:06:20 -0000

On Fri, 14 Dec 2007 18:32:22 -0600
Stephen Montgomery-Smith <stephen@math.missouri.edu> wrote:
> > My bets are on noschg flag.
> Pav, you are exactly right.  I have experienced this many times myself. 
>   After installing the compat5x package you need to do "chflags -R 
> noschg /var/tmp/inst* && rm -rf /var/tmp/inst*" or something like that.
> I think it is a bug in pkg_install, that it doesn't check for the schg 
> flag being set in its temporary file area.  Or maybe it should set the 
> flags in the first place.

	I knew this issue.  So I fixed it with rev#1.16 on make clean.
	But my work was not enough:-(.  How about following patch?

Index: Makefile
===================================================================
RCS file: /home/ncvs/ports/misc/compat5x/Makefile,v
retrieving revision 1.16
diff -u -r1.16 Makefile
--- Makefile	21 Apr 2007 03:24:32 -0000	1.16
+++ Makefile	15 Dec 2007 02:59:30 -0000
@@ -11,7 +11,7 @@
 
 PORTNAME=	compat5x
 PORTVERSION=	5.4.0.8
-PORTREVISION=	8
+PORTREVISION=	9
 CATEGORIES=	misc
 MASTER_SITES=	${MASTER_SITE_LOCAL}
 MASTER_SITE_SUBDIR=lesi/compat5x
@@ -68,6 +68,9 @@
 PLIST_SUB+=	SPARC64="@comment "
 .endif
 
+post-extract:
+	@chflags -R noschg ${WRKSRC} || ${TRUE}
+
 do-install:
 	@${MKDIR} ${TARGET_DIR}
 	(cd ${WRKSRC} && ${INSTALL_DATA} *.so.* ${TARGET_DIR})
@@ -85,7 +88,4 @@
 .endif
 	@${CAT} ${PKGMESSAGE}
 
-pre-clean:
-	@[ -w ${WRKSRC} ] && chflags -R noschg ${WRKSRC} || ${TRUE}
-
 .include <bsd.port.post.mk>