<![CDATA[Content with Style - Comments on Getting phpunit to work with MAMP]]> http://www.contentwithstyle.co.uk/feeds/rss/comments/258 Fri, 10 Sep 2010 00:32:59 -0400 Zend_Feed http://blogs.law.harvard.edu/tech/rss <![CDATA[Content with Style - Comment #1 on Getting phpunit to work with MAMP]]> http://www.contentwithstyle.co.uk/content/getting-phpunit-to-work-with-mamp/#comment-6185 http://www.contentwithstyle.co.uk/content/getting-phpunit-to-work-with-mamp/#comment-6185 Pardon my absolute ignorance in PEAR but

  1. what is the PEAR include path?
  2. my pear.conf file looks like the result of a serialized PHP array. Is this normal? Do add the path to the bottom?

Thanks.

]]> Pardon my absolute ignorance in PEAR but

  1. what is the PEAR include path?
  2. my pear.conf file looks like the result of a serialized PHP array. Is this normal? Do add the path to the bottom?

Thanks.

]]> Tue, 30 Jun 2009 00:08:08 -0400 <![CDATA[Content with Style - Comment #2 on Getting phpunit to work with MAMP]]> http://www.contentwithstyle.co.uk/content/getting-phpunit-to-work-with-mamp/#comment-6306 http://www.contentwithstyle.co.uk/content/getting-phpunit-to-work-with-mamp/#comment-6306
  • The PEAR include path is the path in your php.ini that enables PEAR modules to be included
  • Yes, it is normal, for the pear.conf. No, the path needs to be in the php.ini. Sorry, my fault, I corrected this.
    • ]]>
  • The PEAR include path is the path in your php.ini that enables PEAR modules to be included
  • Yes, it is normal, for the pear.conf. No, the path needs to be in the php.ini. Sorry, my fault, I corrected this.
    • ]]>     Tue, 30 Jun 2009 00:06:15 -0400