> hardcode your own path and let the next sucker repeat the story

fair enough, and now for the heart of the question that I have been dancing
around all along (actually I thought it was obvious) -- what is the best way
to fix this section of code so that we can be done with it once and for all? 
Remove all hard coded paths and require -r and startup from root dir?  ok. 
add the env variable?  ok.  do whatever I am going to do and never post my
patches to start another flame drizzle (as compared to an all out flame war)?
 So, what's to be done?



Reply via email to