[Bug 421241] Review Request: php-ZendFramework - Leading open-source PHP framework

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.

Summary: Review Request: php-ZendFramework - Leading open-source PHP framework


https://bugzilla.redhat.com/show_bug.cgi?id=421241


akahl at iconmobile.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|CLOSED                      |ASSIGNED
           Keywords|                            |Reopened
         Resolution|DEFERRED                    |




------- Additional Comments From akahl at iconmobile.com  2008-03-17 07:18 EST -------
Reopening.

Updated SPEC URL:
http://akahl.fedorapeople.org/php-ZendFramework/php-ZendFramework.spec

Updated SRPM URL:
http://akahl.fedorapeople.org/php-ZendFramework/php-ZendFramework-1.5.0-1.fc8.rc3.src.rpm

--

Since 1.5.0 is about to reach stable, I'm using the release candidates series
for now. All components are split up into subpackages with interdependencies
resolved via manual search and unit tests applied. All components have virtual
requires and provides in the php-Zend(x) namespace.
All significant rpmlint warnings and errors refer to files that are needed by
the unit tests (subpackage -tests) and must not be modified in the distribution,
otherwise complex patches to the tests have to be created and maintained.

One issue remaining is that some unit tests explicitly try to create a cache
directory (grep for cache_dir) locally below their _files directories, thus
failing. Simply symlinking each _files directory below
/var/tmp/php-Zendframework is not a clean solution since most of those already
contain static test data so maybe /var/lib would be a better candidate. Any
suggestions here are welcome.

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.