From owner-freebsd-ports@FreeBSD.ORG  Sun Feb 10 22:29:53 2013
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: 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 B2215447;
 Sun, 10 Feb 2013 22:29:53 +0000 (UTC) (envelope-from meta@vmeta.jp)
Received: from glory.vmeta.jp (7c293911.i-revonet.jp [124.41.57.17])
 by mx1.freebsd.org (Postfix) with ESMTP id 6767D74E;
 Sun, 10 Feb 2013 22:29:52 +0000 (UTC)
Received: from icepick.vmeta.jp (z80.219-127-24.ppp.wakwak.ne.jp
 [219.127.24.80])
 by glory.vmeta.jp (Postfix) with ESMTPSA id A3743A3B;
 Mon, 11 Feb 2013 07:30:10 +0900 (JST)
Date: Mon, 11 Feb 2013 07:29:41 +0900
From: meta <meta@vmeta.jp>
To: Matthew Seaman <matthew@FreeBSD.org>
Subject: Re: WRKDIRPREFIXPORTSDIR?
Message-ID: <20130210222941.GC89392@icepick.vmeta.jp>
References: <e374068bb9d1b93f91570c1a17903064@vmeta.jp>
 <5116C229.6090404@infracaninophile.co.uk>
 <20130210201138.GB89392@icepick.vmeta.jp>
 <51180766.8080802@FreeBSD.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-2022-jp
Content-Disposition: inline
In-Reply-To: <51180766.8080802@FreeBSD.org>
X-Operating-System: FreeBSD 9.1-RELEASE amd64
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: 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: Sun, 10 Feb 2013 22:29:53 -0000

On Sun, Feb 10, 2013 at 08:47:34PM +0000, Matthew Seaman wrote:
> If you have to *set* those variables on redports, then something is
> pretty broken.  The whole point of redports is to test the behaviour of
> ports: having to recode the port specially so it will work there is
> counter productive.

According to Porter's handbook 12.3, working directory is supposed to be
${WRKDIRPREFIX}${PORTSDIR}/subdir/${PORTNAME}, right? But on redports,
its location is different and my port which refers to another port's
working directory fails.

I don't to want to do something redports special. But want to get
actual working directory with same expression even if on redports.
Do I misunderstand something?

Here's the simple Makefile of example port.
https://redports.org/browser/meta/net/example/Makefile
And its build result.
https://redports.org/~meta/20130210221701-9681-104420/example-1.log
> ====================<phase 4: make build>====================
> add_pkg
> ===>  Configuring for example-1
> ===>  Building for example-1
> working directory is supposed to be : /work/usr/ports/net/example/work
> but actually                        : /work/a/ports/net/example/work
> ================================================================

-- 
`whois vmeta.jp | nkf -w`
meta <meta@vmeta.jp>