| Summary | patch for Core to remove duplicate check for PEAR |
| Queue | Horde Framework Packages |
| Type | Enhancement |
| State | Rejected |
| Priority | 1. Low |
| Owners | |
| Requester | vilius (at) lnk (dot) lt |
| Created | 11/18/14 (4151 days ago) |
| Due | |
| Updated | 11/19/14 (4150 days ago) |
| Assigned | |
| Resolved | 11/19/14 (4150 days ago) |
| Milestone | |
| Patch | Yes |
upgrading PEAR :( Upgrading PEAR manually breaks all RPM distributions
because it confuses yum when PEAR upgrade through RPM becomes available.
State ⇒ Rejected
version, is not the same like requiring the pear package. You can use
the pear installer to install horde into a different location, without
having pear installed there too. But we actually do require the pear
package in Horde code.
New Attachment: 0001-No-need-to-check-for-PEAR.patch
Priority ⇒ 1. Low
Patch ⇒ Yes
Milestone ⇒
Queue ⇒ Horde Framework Packages
Summary ⇒ patch for Core to remove duplicate check for PEAR
Type ⇒ Enhancement
State ⇒ New
This also fixes anoying behaviour where all PEAR packages outside of
Horde's channel get updated too.