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 <m...@vmeta.jp>
_______________________________________________
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
