Hi!

A few weeks ago I started using `refuse' files to avoid downloading ports I'm
sure I'll never need (languages I can't speak, for instance). Since then, if
I do anything recursive in the ports tree (a make readmes, for instance),
problems occur. The biggest one is with make readmes. IF I run that from
/usr/ports/www, where I `refuse' w3, I get:

[...snip...]
echo -n '<a href="'w3/README.html'">'"`cd w3; make package-name | sed -e 
's/&/\&amp;/g' -e 's/>/\&gt;/g' -e 's/</\&lt;/g'`</a>: " >> README.html.tmp
cd: can't cd to w3
cat `cd w3; make -V COMMENT` | sed -e 's/&/\&amp;/g' -e 's/>/\&gt;/g' -e 's/</\&lt;/g' 
>> README.html.tmp
cd: can't cd to w3
[...snip...]

The problem seems to be here:

cat `cd w3; make -V COMMENT` | sed -e 's/&/\&amp;/g' -e 's/>/\&gt;/g' -e 's/</\&lt;/g' 
>> README.html.tmp

That's because the make gets executed in /usr/ports/www.

Couldn't we put an

if [ -d w3 ]

in front of any statement which could recurse? In fact, I noticed a check for
PORTSTOP, but I can't understand its use, nor find any documentation for the
various files in Mk.

Anbybody can provide any pointers into this?

TIA, bye,
        Andrea


-- 
            Give a man a fish and you feed him for a day;
     teach him to use the Net and he won't bother you for weeks.



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to