We all have established ways of working, and my own is based on SUSE as
the core OS having switched around a little over the last few years and
simply ended up back with what is simply 'comfortable'. I can control
the remote servers without a problem and keep them up to date security
wise via the SUSE repo's. Managing things not part of the distribution
is a problem.
ALL of the infrastructure running in production is standard distro, so
nginx, PHP and the secondary libraries all install from that. My site
code then simply overlays that base. Since PEAR is part of that suite it
would be nice if it was up to date and while I HAVE taken the time in
the past to push fixes for e_strict and other minor bugs, none of those
submissions have ever been accepted, so have to be maintained on the
side. composer or pickle do not form part of the SUSE distribution so I
have never bothered trying to incorporate them as what I have works. I
have to manually build missing extensions such as imagick but that all
works with the 'SUSE' layout of directories once one has the right build
configuration.
If PEAR is no longer 'official policy' is there any mechanism to replace
it with alternate packages managed via composer and make that the
'official' way of adding userland code modules. So that distributions
have an alternative 'official' mechanism to replace what seems now to
not be wanted?
I did find some threads on 'is PEAR dead' ... from 2003!
--
Lester Caine - G8HFL
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk
Rainbow Digital Media - http://rainbowdigitalmedia.co.uk