Changes between Version 2 and Version 3 of Ticket #37683, comment 4


Ignore:
Timestamp:
Jan 18, 2013, 4:28:03 AM (8 years ago)
Author:
pixilla (Bradley Giesbrecht)
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #37683, comment 4

    v2 v3  
    1414If ports need to be added or updated lets do that.
    1515
    16 There is no MacPorts port that installs the pear package manager application with the intent that it be used by the end user outside a MacPorts port install. If you want to use pear manually on your own then you should install it using gopear, composer or some other method. MacPorts pear ports can depend on and be depended on by other ports and for this to work well MacPorts needs to be in control of the installed files and not have the pear command line package manager changing things out from under it's control by user calls outside MacPorts.
     16There is no MacPorts port that installs the pear package manager application with the intent that it be used by the end user outside a MacPorts port install. If you want to use pear manually on your own then you should install it using gopear, composer or some other method. MacPorts pear ports can depend on and be depended on by other ports and for this to work well MacPorts needs to be in control of the installed files and not have the pear command line package manager changing things out from under it's control by user calls to the pear package manager outside MacPorts.
    1717
    1818> In that case, for **/usr/bin/php** has been used by **pear** as default, all installed command-line utilities from 3rd parties would continue to use **/usr/bin/php**!