Github messages for voidlinux
 help / color / mirror / Atom feed
From: TinfoilSubmarine <TinfoilSubmarine@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: phpMyAdmin: update to 5.2.1
Date: Mon, 07 Aug 2023 14:37:02 +0200	[thread overview]
Message-ID: <20230807123702.PUnX1ffD4nSvw0vNvIrRcadZN2GRJ7prn62eg75ZaPc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44946@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1332 bytes --]

New comment by TinfoilSubmarine on void-packages repository

https://github.com/void-linux/void-packages/pull/44946#issuecomment-1667778612

Comment:
> > Why the change from php8.1 to 8.2? Did the minimum php version requirements change?
> 
> No the minimum is **7.1.3** (https://docs.phpmyadmin.net/en/latest/require.html). But the standard PHP version installed with Void is 8.2 (if you install with **_xbps-install php_** without version - https://voidlinux.org/packages/?arch=x86_64&q=php
> 
> Leaving this to 8.1 installs 8.1 _besides_ 8.2 when people installed the default php. That is imho 1 config file more to maintain. I'd be happy to change it back if you insist...

Just to note: the void-docs [advise against installing the `php` package(s) for non-development purposes](https://docs.voidlinux.org/config/php.html). 

As I'm thinking about it, I don't really understand why we depend on php at all, since the user will have to install the php-fpm, php-apache, or php-cgi for that specific version as well. So all this does is pull in a php that the user may or may not end up using if they installed php8.0 or php8.2 instead. This situation is similar in some ways to postgresql and IIRC is why packages don't generally depend on postgresql and leave it as a task to the user to manually install and configure.

  parent reply	other threads:[~2023-08-07 12:37 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-09 13:55 [PR PATCH] phpMyAdmin: update to version 5.2.1 MeganerdNL
2023-07-09 18:46 ` [PR PATCH] [Updated] " MeganerdNL
2023-07-09 18:49 ` phpMyAdmin: update to 5.2.1 MeganerdNL
2023-07-23 19:22 ` [PR PATCH] [Updated] " MeganerdNL
2023-07-29  8:42 ` MeganerdNL
2023-08-04 15:02 ` TinfoilSubmarine
2023-08-04 15:52 ` MeganerdNL
2023-08-04 21:49 ` williamdes
2023-08-07 12:37 ` TinfoilSubmarine [this message]
2023-08-07 13:12 ` williamdes
2023-08-07 13:22 ` TinfoilSubmarine
2023-08-07 13:38 ` williamdes
2023-08-08  2:18 ` TinfoilSubmarine
2023-08-08  5:53 ` MeganerdNL
2023-08-08  5:54 ` MeganerdNL
2023-08-08  7:30 ` MeganerdNL
2023-08-08  8:42 ` williamdes
2023-08-08  8:42 ` williamdes
2023-08-08 12:47 ` TinfoilSubmarine
2023-08-08 12:49 ` TinfoilSubmarine
2023-08-08 14:34 ` TinfoilSubmarine
2023-08-08 14:35 ` TinfoilSubmarine
2023-08-08 15:36 ` [PR PATCH] [Updated] " MeganerdNL
2023-08-08 15:41 ` MeganerdNL
2023-08-11  8:59 ` [PR PATCH] [Updated] " MeganerdNL
2023-09-15 10:15 ` MeganerdNL
2023-12-15  1:46 ` github-actions
2023-12-30  1:45 ` [PR PATCH] [Closed]: " github-actions
2023-12-30 11:11 ` williamdes

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230807123702.PUnX1ffD4nSvw0vNvIrRcadZN2GRJ7prn62eg75ZaPc@z \
    --to=tinfoilsubmarine@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).