I would like to register OpenLiteSpeed with GURU, but the PHP ebuild is not litespeed compliant, so I would like you to support it. Reproducible: Always
This is a large undertaking, and the PHP project recently became empty. Adding litespeed support isn't just another ./configure flag; it's an entirely new SAPI. We'd need to support it not only in the four dev-lang/php slots, but also in a new version of app-eselect/eselect-php. Without the OpenLiteSpeed server in the main ::gentoo repository and without a dedicated developer, it's probably not going to happen. I'm not saying it's not a desirable goal, I'm just trying to set the right expectations so you're not disappointed if no progress is made.
Thank you very much. I now understand the difficulty of adding litespeed support to existing php. For example, how about adding the lsphp used by openlitespeed to guru? It would be a tough requirement since we would effectively have two separate repositories of php (with separate administrators). I didn't think openlitespeed was important enough to be in the main gentoo repository, so my first thought was to put it in the guru repository...
(In reply to trakrailysurely from comment #2) > Thank you very much. > I now understand the difficulty of adding litespeed support to existing php. > For example, how about adding the lsphp used by openlitespeed to guru? > > It would be a tough requirement since we would effectively have two separate > repositories of php (with separate administrators). You would still have a lot of work to do to get it in GURU. Users are able to install different slots (versions) of PHP, and then switch between them with e.g. $ eselect php set cli php8.0 $ eselect php set apache2 php8.2 That's all managed by app-eselect/eselect-php, which would need to know about litespeed in addition to cgi, fpm, cli, apache2, and phpdbg. So your first project would be to update eselect-php with support for litespeed: https://gitweb.gentoo.org/proj/eselect-php.git Then you'd still have to add litespeed support to the four php slots. Then finally you have to the OpenLiteSpeed server packaged and working. None of it is impossible but you're probably looking at a day or two of work. If you do get it working, I'd be happy to merge the PHP/eselect-php changes into ::gentoo.
Thank you very much. I found out that I need to support eselect-php first, so I created a separate bug. https://bugs.gentoo.org/908996 My concern is that I don't know if it is safe to do the work of being able to switch php first, since I need to support the lsphp command instead of php in order to run php commands in openlitespeed.
(In reply to trakrailysurely from comment #4) > > My concern is that I don't know if it is safe to do the work of being able > to switch php first, since I need to support the lsphp command instead of > php in order to run php commands in openlitespeed. It should be safe, eselect-php must be able to detect that the litespeed SAPI is disabled (or not existing yet). For example, my PHP is built without FPM, and # eselect php list fpm (none found) Of course, to test that it actually works, you would need to add the litespeed support to your local php, too.
