From owner-freebsd-tex@FreeBSD.ORG Sat Aug 23 19:19:10 2014 Return-Path: Delivered-To: freebsd-tex@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9D5EBEDD; Sat, 23 Aug 2014 19:19:10 +0000 (UTC) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 52E83342E; Sat, 23 Aug 2014 19:19:10 +0000 (UTC) Received: from pi by home.opsec.eu with local (Exim 4.82 (FreeBSD)) (envelope-from ) id 1XLGqE-000Ltw-H0; Sat, 23 Aug 2014 21:19:10 +0200 Date: Sat, 23 Aug 2014 21:19:10 +0200 From: Kurt Jaeger To: Hiroki Sato Subject: Re: TeXLive 2014 Message-ID: <20140823191910.GZ9400@home.opsec.eu> References: <20140823174220.GA46087@misty.eyesbeyond.com> <20140824.034506.732618146848153013.hrs@allbsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20140824.034506.732618146848153013.hrs@allbsd.org> Cc: freebsd-tex@FreeBSD.org, freebsd-ports@FreeBSD.org X-BeenThere: freebsd-tex@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting TeX and related applications to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Aug 2014 19:19:10 -0000 Hi! > gl> Error: 'share/texmf-var/web2c/euptex/uplatex.fmt' is referring to /usr/ports/japanese/tex-ptex/work/stage > gl> > gl> In this case the .fmt files are a needed file for things to work. > This is reproducible and has also been filed as PR 192933. I am > wondering if I should fix this and how to do it if should. I agree > that it is better to fix them if possible, but it is harmless in this > case and difficult to properly fix it. > > foo.fmt and foo.log which are generated for a TeX format "foo". They > contain ${STAGEDIR} because they are processed within the directory, > but they are just recorded, not used as pathname. Although we can > replace the pathnames by using sed(1) in foo.log since it is a plain > text, it is difficult for foo.fmt. One solution could be a change to /usr/ports/Mk/Scripts/qa.sh which tells it to ignore tex-related .fmt and .log files ? -- pi@opsec.eu +49 171 3101372 6 years to go !