[nycbug-talk] Make package-recursive problem

[Matt Juszczak]

> If it's a prod webserver, you might want to just copy the .so files so you 
> can leave it for now in a working shape and spend tomorrow, rested, fixing 
> the ports dependencies :)

It's a webserver that will be production.  It's out of production now.

I attempted to fix the problem by doing:

cd /usr/ports/www/php5-session && make package-recursive

which did not fix the problem.  In fact, it created more "no files" 
packages:

s507# pkg_info -L php5-session-5.2.9
Information for php5-session-5.2.9:

Files:

s507#


But I just went and manually built a package just for that module:

cd /usr/ports/www/php5-session && make clean && make deinstall && make 
package

and it worked:

s507# pkg_info -L php5-session-5.2.9
Information for php5-session-5.2.9:

Files:
/usr/local/lib/php/20060613/session.so
/usr/local/include/php/ext/session/config.h
/usr/local/include/php/ext/session/mod_files.h
/usr/local/include/php/ext/session/mod_mm.h
/usr/local/include/php/ext/session/mod_user.h
/usr/local/include/php/ext/session/php_session.h



My only question at this point is... it seems like all these modules do is 
make .so files right?  So if I make clean and recompile them, without 
creating a new php5 master package, it should still all work as long as 
its the same version.... correct?  Or are there potential issues by 
building these php5-* modules separately from php5? (doing a make clean 
first)

-M