From: the-eater <the-eater@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: php: update to 8.0.7 & xdebug: update to 3.0.4
Date: Sun, 27 Jun 2021 11:08:30 +0200 [thread overview]
Message-ID: <20210627090830.CnRI_ERPpAscf4u16zOC0BMp9QnRmXiRFi1D80byHAY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31668@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 567 bytes --]
New comment by the-eater on void-packages repository
https://github.com/void-linux/void-packages/pull/31668#issuecomment-869129176
Comment:
@paper42 Yea we could I've been playing around with the idea of splitting php into php7 and php8 and using xbps-alternatives to give you A Central PHP.
I'm however not sure how trivial it is to rename a package
it might even make more sense to let the php package be and start a new php8 package
(having php versions side to side is trivial since it's basically baked into php itself so that part won't be an issue)
next prev parent reply other threads:[~2021-06-27 9:08 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-26 17:30 [PR PATCH] " the-eater
2021-06-26 17:49 ` [PR PATCH] [Updated] " the-eater
2021-06-26 19:56 ` [PR REVIEW] " ericonr
2021-06-26 19:56 ` ericonr
2021-06-26 19:56 ` ericonr
2021-06-26 19:59 ` the-eater
2021-06-26 22:30 ` the-eater
2021-06-26 22:38 ` [PR PATCH] [Updated] " the-eater
2021-06-26 22:53 ` [PR REVIEW] " the-eater
2021-06-27 4:05 ` ericonr
2021-06-27 4:05 ` ericonr
2021-06-27 4:05 ` ericonr
2021-06-27 4:05 ` ericonr
2021-06-27 4:05 ` ericonr
2021-06-27 4:05 ` ericonr
2021-06-27 8:15 ` paper42
2021-06-27 9:04 ` [PR REVIEW] " the-eater
2021-06-27 9:08 ` the-eater [this message]
2021-06-27 11:37 ` the-eater
2021-06-27 11:41 ` [PR PATCH] [Updated] " the-eater
2021-06-27 11:58 ` [PR PATCH] [Closed]: " the-eater
2021-06-27 14:22 ` [PR REVIEW] " ericonr
2021-06-27 14:48 ` the-eater
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=20210627090830.CnRI_ERPpAscf4u16zOC0BMp9QnRmXiRFi1D80byHAY@z \
--to=the-eater@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).