On Mon, Dec 19, 2022 at 3:40 PM Jelle van der Waa <je...@vdwaa.nl> wrote: > I don't object against providing an older PHP but why is it named > php-legacy? We don't really have a policy for this, but it feels > inconsistent versus the current php7, ruby2.7 package. (Ofcourse > nodejs-lts-gallium is then also inconsistent but at least that is > clearly named as that upstream).
I looked for several options regarding naming and ended up with either "-old" or "-legacy". I chose the later as it has a less negative tone and there are precedence for it in naming different releases branches. We also have similar concepts with libreoffice-still and libreoffice-fresh or nginx and nginx-mainline. Numbers couldn't be used here as both branches will get updated regularly. php-legacy will be bumped to version 8.2 and even 9.0 some day. So the difference is that I didn't want to provide a specific version but two different release branches. This makes it easier for users to update and packagers to maintain. It should be inline with Arch's rolling release model. Greetings, Pierre -- Pierre Schmitz, https://pierre-schmitz.com
