From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: php/php8.0/php8.1 and composer/composer8.0/composer8.1: add alternatives groups.
Date: Tue, 09 Aug 2022 01:37:34 +0200 [thread overview]
Message-ID: <20220808233734.NS9bpg3vpozTo43ZVtuPFc432ndUWEBpb1YH3kUGH5M@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38536@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 451 bytes --]
New comment by paper42 on void-packages repository
https://github.com/void-linux/void-packages/pull/38536#issuecomment-1208728017
Comment:
I think this is a bit too fragile and we should wait with this for php 7.4 EOL which should be in November. Which /usr/bin/php gets chosen when the user has php (7) and php8.0 installed? Are we sure it always works as expected and won't break the setup for some users who rely on /usr/bin/php being php7, etc?
next prev parent reply other threads:[~2022-08-08 23:37 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-08 16:45 [PR PATCH] " TinfoilSubmarine
2022-08-08 23:37 ` paper42 [this message]
2022-08-09 18:08 ` Chocimier
2022-08-09 18:43 ` [PR PATCH] [Updated] " TinfoilSubmarine
2022-08-09 18:45 ` TinfoilSubmarine
2022-08-29 12:37 ` [PR PATCH] [Updated] [NOMERGE] php/composer: turn into meta package as 7.4 is EOL; php8.[01] and composer8.[01]: " TinfoilSubmarine
2022-08-29 12:49 ` TinfoilSubmarine
2022-08-29 12:58 ` [PR PATCH] [Updated] [WIP] " TinfoilSubmarine
2022-08-29 13:10 ` TinfoilSubmarine
2022-08-29 13:18 ` TinfoilSubmarine
2022-08-29 13:47 ` TinfoilSubmarine
2022-08-29 14:57 ` TinfoilSubmarine
2022-08-30 18:42 ` TinfoilSubmarine
2022-08-30 21:19 ` [PR REVIEW] " paper42
2022-08-31 12:41 ` [PR PATCH] [Updated] " TinfoilSubmarine
2022-08-31 12:44 ` [PR REVIEW] " TinfoilSubmarine
2022-11-17 14:33 ` [PR PATCH] [Updated] " TinfoilSubmarine
2022-11-27 10:33 ` paper42
2022-11-28 20:01 ` [PR PATCH] [Updated] " TinfoilSubmarine
2022-12-01 13:15 ` TinfoilSubmarine
2022-12-04 13:52 ` [PR REVIEW] " paper42
2022-12-04 13:52 ` paper42
2022-12-04 13:52 ` paper42
2022-12-04 13:52 ` paper42
2022-12-04 13:52 ` paper42
2022-12-06 15:45 ` TinfoilSubmarine
2022-12-06 17:34 ` [PR PATCH] [Updated] " TinfoilSubmarine
2022-12-06 17:35 ` [PR REVIEW] " TinfoilSubmarine
2022-12-06 19:14 ` paper42
2022-12-06 19:14 ` paper42
2022-12-07 14:25 ` [PR PATCH] [Updated] " TinfoilSubmarine
2022-12-08 18:42 ` [PR REVIEW] " TinfoilSubmarine
2022-12-15 17:10 ` paper42
2022-12-15 17:47 ` TinfoilSubmarine
2022-12-25 0:00 ` paper42
2022-12-25 0:03 ` paper42
2023-01-04 20:41 ` TinfoilSubmarine
2023-01-20 15:38 ` [PR PATCH] [Updated] " TinfoilSubmarine
2023-01-20 15:43 ` [PR REVIEW] " TinfoilSubmarine
2023-02-15 19:29 ` [PR PATCH] [Updated] " TinfoilSubmarine
2023-02-21 18:34 ` [PR REVIEW] " TinfoilSubmarine
2023-02-21 23:50 ` paper42
2023-02-28 22:36 ` paper42
2023-03-01 13:23 ` [PR PATCH] [Updated] " TinfoilSubmarine
2023-03-01 13:26 ` [PR REVIEW] " TinfoilSubmarine
2023-03-02 21:25 ` paper42
2023-03-02 21:58 ` [PR PATCH] [Updated] " TinfoilSubmarine
2023-03-02 21:59 ` [PR REVIEW] " TinfoilSubmarine
2023-03-04 22:05 ` [PR PATCH] [Merged]: " paper42
2023-04-08 3:34 ` jchook
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=20220808233734.NS9bpg3vpozTo43ZVtuPFc432ndUWEBpb1YH3kUGH5M@z \
--to=paper42@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).