Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 30 Sep 2000 16:48:19 -0300
From:      "Mario Sergio Fujikawa Ferreira" <>
To:        Satoshi - Ports Wraith - Asami <asami@FreeBSD.ORG>
Subject:   Re: RFC: Ports layout reorganization (Re: ports tree idea:     Combine DESCR and COMMENT)
Message-ID:  <>
In-Reply-To: <>; from asami@FreeBSD.ORG on Sat, Sep 30, 2000 at 04:26:51AM -0700
References:  <"Jeffrey <> <> <> <>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
On Sat, Sep 30, 2000 at 04:26:51AM -0700, Satoshi - Ports Wraith - Asami wrote:
> The %%DESCR%% substitution in README.port actually doesn't work when
> MASTERDIR is set relative to ${PORTSDIR} and ${PORTSDIR} is a symlink
> to something else, but you are not supposed to use ${PORTSDIR} in a
> MASTERDIR definition so we should be safe.  (The old README.port
> wouldn't have worked at all for ports with MASTERDIR or its own idea
> of DESCR anyway.)

	On the light of this observation, I am proposing the
following patch to the porters-handbook. Or, something like that.

		Mario Ferreira


diff -ruN /usr/doc/en_US.ISO_8859-1/books/porters-handbook/book.sgml en_US.ISO_8859-1/books/porters-handbook/book.sgml
--- /usr/doc/en_US.ISO_8859-1/books/porters-handbook/book.sgml	Thu Sep 28 00:31:29 2000
+++ en_US.ISO_8859-1/books/porters-handbook/book.sgml	Sat Sep 30 16:34:19 2000
@@ -1321,6 +1321,13 @@
         <link linkend="porting-pkgname"><makevar>PKGNAMESUFFIX</makevar></link> so
         the packages will have different names.</para>
+      <para>However, your port should not use ${PORTSDIR} to set
+	<makevar>MASTERDIR</makevar> as pointed out by the Ports
+	Wraith. Use a relative definition if you must, e.g.,
+	MASTERDIR=${.CURDIR}/../other_port_dir_relative_path/.
+	Just check the example below.</para>
       <para>This will be best demonstrated by an example.  This is part of

To Unsubscribe: send mail to
with "unsubscribe freebsd-doc" in the body of the message

Want to link to this message? Use this URL: <>