Date: Wed, 17 Sep 1997 17:17:31 +0900 From: itojun@itojun.org To: asami@cs.berkeley.edu (Satoshi Asami) Cc: tg@ihf.rwth-aachen.de, ports@freebsd.org Subject: Re: portlint check to dependency pathname Message-ID: <21220.874484251@itojun.csl.sony.co.jp> In-Reply-To: asami@cs.berkeley.edu (Satoshi Asami)'s message of Wed, 17 Sep 1997 01:15:44 -0700 (PDT). <199709170815.BAA19783@silvia.HIP.Berkeley.EDU> References: <199709170815.BAA19783@silvia.HIP.Berkeley.EDU>
next in thread | previous in thread | raw e-mail | index | archive | help
> * I'd like to avoid hard-coding name of port directory (x11/libsx,
> * for example) into portlint. I may be able to check if there's
> * directory named ../../x11/libsx. Is it enough for you?
> * If there's any other ideas to check this case, please let me know.
> * (is there any possibility for more-than-two-layers port subdir?
> * In that case, it becomes harder)
>Can't you just use the whole "${PORTSDIR}/x11/libsx" thing?
Yes I plan to use that.
I was unsure about the interpretation of ${PORTSDIR} in portlint.
(Should it be "/usr/ports", or should it be "../..". While testing
a port people may not be using /usr/ports...)
>By the
>way, don't forget the dependencies might take an optional argument, as
>in
>file:${PORTSDIR}/category/dir:target
itojun
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?21220.874484251>