[dev] Switching from PEAR to Composer

Kieran Brahney kieran at supportpal.com
Wed Oct 28 12:21:49 UTC 2020


Hello,

I've been referred to this mailing list by Jan over at
https://github.com/composer/composer/issues/8778#issuecomment-717744599

We (SupportPal) have recently switched to using the Horde IMAP client for a
variety of reasons, but mainly due to lack of XOAUTH2 support in the
php-imap extension. The library is currently integrated via Composer and
the Horde PEAR repository. As you're aware Composer 2.0 has now dropped
support for PEAR.

I am not too familiar with the Horde code base beyond using it as an
application.That said, given we currently only use the Horde IMAP client
(and its related components) we are happy to help upgrade and test these
parts of Horde.

I've read over the past months discussions on this mailing list and also
checked https://github.com/horde/Imap_Client. It looks like the majority of
work has been undertaken by Ralf, specifically -
https://lists.horde.org/archives/dev/Week-of-Mon-20201005/029494.html. I
don't believe any work has started on upgrading this component? If someone
would be so kind to describe how we can help I would be very grateful.

If ChristophWurst (from the aforementioned GitHub issue) is subscribed to
the mailing list then we should coordinate to avoid clashing! You're
welcome to email me directly once we know what work is required.

Thanks for your time and consideration!

----
Best Regards,

Kieran Brahney
*SupportPal Limited*

Join us on Facebook https://www.facebook.com/supportpal.limited
Follow us on Twitter http://twitter.com/SupportPal

This e-mail is intended solely for the addressee and is
strictly confidential. If you are not the intended addressee, please do not
read, print, retransmit, store or act in reliance on it or any attachments.
Instead please notify me immediately and delete the message from your
computer.

E-mail transmission cannot be guaranteed to be secure or error free and I
accept no liability for changes made to this e-mail (and any attachments)
after it was sent or for viruses arising as a result of this e-mail
transmission.


More information about the dev mailing list