Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 11 Feb 2013 07:29:41 +0900
From:      meta <meta@vmeta.jp>
To:        Matthew Seaman <matthew@FreeBSD.org>
Cc:        ports@freebsd.org
Subject:   Re: WRKDIRPREFIXPORTSDIR?
Message-ID:  <20130210222941.GC89392@icepick.vmeta.jp>
In-Reply-To: <51180766.8080802@FreeBSD.org>
References:  <e374068bb9d1b93f91570c1a17903064@vmeta.jp> <5116C229.6090404@infracaninophile.co.uk> <20130210201138.GB89392@icepick.vmeta.jp> <51180766.8080802@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
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>



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130210222941.GC89392>