Date: Thu, 20 Jul 2006 21:45:21 GMT From: Gabor Kovesdan <gabor@FreeBSD.org> To: Perforce Change Reviews <perforce@FreeBSD.org> Subject: PERFORCE change 102032 for review Message-ID: <200607202145.k6KLjLaB060153@repoman.freebsd.org>
next in thread | raw e-mail | index | archive | help
http://perforce.freebsd.org/chv.cgi?CH=102032 Change 102032 by gabor@gabor_spitfire on 2006/07/20 21:44:30 - Document TARGETDIR - s/here/there/ Affected files ... .. //depot/projects/soc2006/gabor_docs/porters-handbook/book.sgml#8 edit Differences ... ==== //depot/projects/soc2006/gabor_docs/porters-handbook/book.sgml#8 (text+ko) ==== @@ -6866,7 +6866,11 @@ definitely wrong, but you can use <makevar>LOCALBASE_REL</makevar> if you need a variable relative to <makevar>DESTDIR</makevar>. Similarly, you can use <makevar>LINUXBASE_REL</makevar> and - <makevar>X11BASE_REL</makevar> variables as well.</para> + <makevar>X11BASE_REL</makevar> variables as well. + <makevar>PREFIX</makevar> is an absolute path. but relative + to <makewar>DESTDIR</makevar>. If you want to refer to the + fully qualified destination you can use <makevar>TARGETDIR</makevar>, + which resolves to <makevar>DESTDIR</makevar>/<makevar>PREFIX</makevar>.</para> <para>You have to use these variables correctly in your ports <filename>Makefile</filename>, esepecially in @@ -6880,7 +6884,7 @@ <para>In packing lists, or in <filename>pkg-*</filename> scripts you can still use <literal>%%LOCALBASE%%</literal>, <literal>%%LINUXBASE%%</literal> and <literal>%%X11BASE%%</literal> - expansions, since they represent relative paths here. This ambiguity + expansions, since they represent relative paths there. This ambiguity can be frustrating at first, but this actually simplifies the process of writing <makevar>DESTDIR</makevar>-compliant ports. We did not use to have <makevar>DESTDIR</makevar> support by our ports infrastructure,
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200607202145.k6KLjLaB060153>