Comments for "PEAR_Exception"

» Submit Your Comment
Comments are only accepted during the "Proposal" phase. This proposal is currently in the "Finished" phase.
» Comments
  • Markus Tacker  [2012-04-20 15:57 UTC]

    > Suggest someone else do a release of the pear installer with an appropriate explanation of how to fix any upgrade problems (pear upgrade pear && pear install PEAR_Exception)

    Couldn't this just be done automatically by depending PEAR on PEAR_Exception?
  • Till Klampaeckel  [2012-04-20 16:26 UTC]

    I agree with this. :) Thanks for putting up this proposal!
  • Brett Bieber  [2012-04-20 16:30 UTC]

    Very big +1 from me.
  • Daniel O'Connor  [2012-04-20 16:39 UTC]

    >> Suggest someone else do a release of the pear installer with an appropriate explanation of how to fix any upgrade problems (pear upgrade pear && pear install PEAR_Exception)

    > Couldn't this just be done automatically by depending PEAR on PEAR_Exception?

    Well, yeah, but I'd have to never set PEAR_Exception's min php version to 5 unfortunately!

    I know we've had the discussion a few times around "who uses PHP4 anymore, anyway?" - but no one has made the call.

    This is just one more piece being chipped away.
  • Helgi Þormar Þorbjörnsson  [2012-04-20 16:45 UTC]

    I think this RFC is a bit misguided.

    I have had this on my plans for a long time but never found the time - I would love if someone took on this initiative.

    The package xml for this is already ready: https://github.com/pear/pear-core/blob/master/package-Exception.xml - for the most part.

    It didn't help that PEAR had deps on PHP 4, so the only viable option was to make PEAR_Exception depend on PHP 4 as well. That way PEAR could depend on PEAR_Exception and not the other way around, thus on the new PEAR update people would get PEAR_Exception.

    If we move PEAR it self to have a min dep on PHP 5 (5.1.6 or 5.2 perhaps) then PEAR_Exception can dep on PHP 5 as well and everyone is happy. No confusion.

    Package authors can them self do releases (or QA) with a new dep on PEAR_Exception instead of PEAR, but it won't be required to do a mass updated on all packages.

    I want to see this done but not in the confusing manner proposed.
  • Till Klampaeckel  [2012-04-20 17:11 UTC]

    For myself this is not about a PHP4 dependency, it's about all the packages I have to install when a package depends on "PEAR" just for the exception.

    So for example, I depend on HTTP_Request2 which uses PEAR_Exception, in return I have the following packages installed along with it:

    * xml_util (1.2.1)
    * structures_graph (1.0.4)
    * pear_frontend_web (0.4)
    * pear_frontend_gtk (0.4.0)
    * pear (1.9.4)
    * console_getopt (1.3.1)
    * archive_tar (1.3.10)

    Strictly speaking, they are not required for HTTP_Request2, but they are installed because of the PEAR dependency.
  • Daniel O'Connor  [2012-04-20 17:40 UTC]

    ab675ef..ae590f3 should be the last few commits to bring back that package-Exception.xml as package.xml, and make it valid (todo: kill package-Exception.xml from the pear-core repo)
  • Till Klampaeckel  [2012-04-28 21:43 UTC]

    Can we vote?