It would be possible to be se satis for composer support. It's static files only and can be committed and generated. Would infra somehow support this when the scripts were provided?
On Tue, Mar 21, 2017, at 17:26, Sven Rautenberg wrote: > The usual way to distribute PHP libraries today is via Composer > (the dependency manager) and packagist.org (the central package > registry site). > > Am 20. März 2017 20:58:22 MEZ schrieb Chris Mattmann > <[email protected]>: >> The Apache OODT project does try to publish PHP client code for >> >> our software to pear.apache.org (in fact, Gav has helped us do so >> >> in the past). >> >> >> >> Can some replacement be provided? >> >> >> >> Thanks, >> >> Chris >> >> >> >> >> >> >> >> >> >> On 3/20/17, 12:43 PM, "Daniel Gruno" <[email protected]> wrote: >> >> >> >> Hi folks, >> >> >> >> as the subject says, we'll be shutting down pear.apache.org in >> about 30 >> >> days from now. There is no immediate replacement scheduled, as >> the >> >> service is not being actively used or maintained. Please make >> sure you >> >> are not actively relying on this service. If you have any >> questions or >> >> comments, please direct them to [email protected] >> >> >> >> With regards, >> >> Daniel on behalf of ASF Infra. >> >> >> >> >> > > Mit freundlichen Grüßen > > Sven Rautenberg
