Date: Mon, 25 Mar 1996 19:18:50 -0800 From: asami@cs.berkeley.edu (Satoshi Asami) To: james@nexis.net Cc: freebsd-ports@freebsd.org Subject: Re: Question about dependencies Message-ID: <199603260318.TAA19353@sunrise.cs.berkeley.edu> In-Reply-To: <Pine.BSF.3.91.960325181048.795F-100000@nexis.net> (message from James FitzGibbon on Mon, 25 Mar 1996 18:12:17 -0500 (EST))
next in thread | previous in thread | raw e-mail | index | archive | help
* I don't want to just use DEPENDS, because then it will re-build FVWM
* every time anyone installs the port.
Right. It's a good idea to avoid DEPENDS if you can.
* Likewise, I can't use the
* existance of the fvwm binary to be sure, because it might not have been
* installed as a port and thus be missing said modules.
Don't worry about it too much. The ports collection is designed to be
closed by itself, and many ports will fail if people start mixing the
ports collection to un-ports-collection programs....
* If I use RUN_DEPENDS,
* then it does work, but somehow the line :
*
* RUN_DEPENDS= ${PREFIX}/lib/X11/fvwm/FvwmClean:${PORTSDIR}/x11/fvwm
*
* Seems to be kludgey to me. Is there a more elegant way of achieving this ?
If you really want to check it, this is exactly what you're supposed
to do.
* Next question: How do I do a dependency upon a file just existing if it's
* not an executable. RUN_DEPENDS won't work if the existing file is mode
* 644 for example. Is there a FILE_DEPENDS variable, or should I try to
* hack that into my Makefile for now?
The latest bsd.port.mk (I added this on 11/26 last year, or revision
1.188) should work fine. This is the commit message:
===
Make the {FETCH,BUILD,RUN}_DEPEND targets work with non-executable files
too. Basically, if the name starts with a "/", it's tested with "test -e";
otherwise, it's tested with "witch -s".
===
(of course, "witch" is a typo of "which" ;)
* And finally: Assuming this works correctly, I've got a few
* more programs I'd like to port. Should I be concerned about getting a
* @freebsd.org address and commit privilidges to avoid bothering someone
* else every time a change comes out? If so, how do I go about it ?
I can work with you on that. First, please read the cvs manpage (I
think Rod used to say something like "1. read the manpage 2. read it
again 3. read it again" :) and make sure you understand what it's all
about.
Also, check out the porting section of the handbook
(http://www.freebsd.org/handbook/porting.html). After you're
comfortable with both ports and cvs, please send me a note.
Satoshi
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199603260318.TAA19353>