Github messages for voidlinux
 help / color / mirror / Atom feed
* [ISSUE] [RFC] Split php package into php7 and php8
@ 2021-06-27 11:31 the-eater
  2021-06-28 16:05 ` Chocimier
                   ` (20 more replies)
  0 siblings, 21 replies; 22+ messages in thread
From: the-eater @ 2021-06-27 11:31 UTC (permalink / raw)
  To: ml

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

New issue by the-eater on void-packages repository

https://github.com/void-linux/void-packages/issues/31678

Description:
Currently we only provide one leading php version which is currently pinned at php 7.4 (the latest supported version of php 7)

this has generally not been a problem since the migration from php 5.6 to php 7.0 was rather painless, however with php 8 this is not as painless and because of new features and changes in behavior loads of projects may or will be broken.

but php 8 is currently the leading version (and also i want to play with it) and waiting for adoption seems a bit misguided and annoying for everyone (me) wanting to adopt php 8.

To resolve this situation I am proposing the following

- [ ] Move `php` to `php7`
- [ ] Create xbps-alternatives group for php which symlinks the correct folders and binaries
- [ ] Create new `php8` package
- [ ] Copy and move all php extensions to `php7` and `php8` prefixed packages (these are `php-apcu`, `php-ast`, `php-igbinary` and `php-imagick`)
- [ ] Provide a wrapper script for `pecl` (from the new `pear` package) (`pecl7` and `pecl8`) which sets the correct program suffix for compiling pecl extensions

both php versions will have matching postfixes e.g. `php7` will provide `php7` and it's config files will live in `/etc/php7` etc.

If we do migration of `php` -> `php7` correctly there should be no conflicts, we can move the `/etc/php` to `/etc/php7` directory if present.

php packages directly affected:

`phpMyAdmin` and `ampache`: DIY hosting package, so can be kept an exercise to the reader
`phoronix-test-suite`: We need to check for php8 support, if there is none we can pin and patch it to use php7
`composer`: Works on both php7 and php8 so can be kept as is
`pear` (replaces php-pear): Works on both php7 and php8 and can be mostly kept as is except the pecl part, which is explained in my TODO list
`php-*`: Are all bundled extensions with the exception of the items listed above, but these can all be migrated alike php

Before I do any of this I would like some feedback if this the correct way forward or if there's a better way to do so

/cc @paper42 (because you raised this issue)

Fuck I am basically back at doing the shit I did at my first job

^ permalink raw reply	[flat|nested] 22+ messages in thread

* Re: [RFC] Split php package into php7 and php8
  2021-06-27 11:31 [ISSUE] [RFC] Split php package into php7 and php8 the-eater
@ 2021-06-28 16:05 ` Chocimier
  2021-06-28 16:08 ` the-eater
                   ` (19 subsequent siblings)
  20 siblings, 0 replies; 22+ messages in thread
From: Chocimier @ 2021-06-28 16:05 UTC (permalink / raw)
  To: ml

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

New comment by Chocimier on void-packages repository

https://github.com/void-linux/void-packages/issues/31678#issuecomment-869810942

Comment:
Sounds good with exception of

> move the `/etc/php` to `/etc/php7`

This is breaking change for people who maintain configuration in /etc/php, same for custom modules in /usr.
Similar postgresql upgrade was done by leaving old series under old name and paths, until it reach EOL.

^ permalink raw reply	[flat|nested] 22+ messages in thread

* Re: [RFC] Split php package into php7 and php8
  2021-06-27 11:31 [ISSUE] [RFC] Split php package into php7 and php8 the-eater
  2021-06-28 16:05 ` Chocimier
@ 2021-06-28 16:08 ` the-eater
  2021-06-28 16:14 ` the-eater
                   ` (18 subsequent siblings)
  20 siblings, 0 replies; 22+ messages in thread
From: the-eater @ 2021-06-28 16:08 UTC (permalink / raw)
  To: ml

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

New comment by the-eater on void-packages repository

https://github.com/void-linux/void-packages/issues/31678#issuecomment-869814003

Comment:
I was thinking of making that folder part of the xbps-alternatives, so it stays consistent for everything?

^ permalink raw reply	[flat|nested] 22+ messages in thread

* Re: [RFC] Split php package into php7 and php8
  2021-06-27 11:31 [ISSUE] [RFC] Split php package into php7 and php8 the-eater
  2021-06-28 16:05 ` Chocimier
  2021-06-28 16:08 ` the-eater
@ 2021-06-28 16:14 ` the-eater
  2021-06-28 16:16 ` Duncaen
                   ` (17 subsequent siblings)
  20 siblings, 0 replies; 22+ messages in thread
From: the-eater @ 2021-06-28 16:14 UTC (permalink / raw)
  To: ml

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

New comment by the-eater on void-packages repository

https://github.com/void-linux/void-packages/issues/31678#issuecomment-869818481

Comment:
I will say that it's the part I have most trouble with getting a good solution for. the config has no breaking changes and can be carried over from php7 -> php8 and once we go EOL it might be desirable to just copy it over to give an easy transition

^ permalink raw reply	[flat|nested] 22+ messages in thread

* Re: [RFC] Split php package into php7 and php8
  2021-06-27 11:31 [ISSUE] [RFC] Split php package into php7 and php8 the-eater
                   ` (2 preceding siblings ...)
  2021-06-28 16:14 ` the-eater
@ 2021-06-28 16:16 ` Duncaen
  2021-06-28 16:17 ` Duncaen
                   ` (16 subsequent siblings)
  20 siblings, 0 replies; 22+ messages in thread
From: Duncaen @ 2021-06-28 16:16 UTC (permalink / raw)
  To: ml

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

New comment by Duncaen on void-packages repository

https://github.com/void-linux/void-packages/issues/31678#issuecomment-869820069

Comment:
> I was thinking of making that folder part of the xbps-alternatives, so it stays consistent for everything?

With configuration files if they are changed xbps won't delete the configuration file and therefor won't be able to delete the directory, xbps would not error out because it currently does not take alternatives into account for file checks, but if it would do that it would simply error out saying that the "type" of `/etc/php` changed from directory to symlink, but it is not able to delete the directory because it contains files not removed by any package.

^ permalink raw reply	[flat|nested] 22+ messages in thread

* Re: [RFC] Split php package into php7 and php8
  2021-06-27 11:31 [ISSUE] [RFC] Split php package into php7 and php8 the-eater
                   ` (3 preceding siblings ...)
  2021-06-28 16:16 ` Duncaen
@ 2021-06-28 16:17 ` Duncaen
  2021-06-28 16:19 ` the-eater
                   ` (15 subsequent siblings)
  20 siblings, 0 replies; 22+ messages in thread
From: Duncaen @ 2021-06-28 16:17 UTC (permalink / raw)
  To: ml

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

New comment by Duncaen on void-packages repository

https://github.com/void-linux/void-packages/issues/31678#issuecomment-869820069

Comment:
> I was thinking of making that folder part of the xbps-alternatives, so it stays consistent for everything?

With configuration files if they are changed xbps won't delete the configuration file and therefor won't be able to delete the directory. xbps would not error out because it currently does not take alternatives into account for file checks.

If xbps it would also add alternatives to the file checks, it would simply error out saying that the "type" of `/etc/php` changed from directory to symlink, but it is not able to delete the directory because it contains files not removed by any package in the transaction.

^ permalink raw reply	[flat|nested] 22+ messages in thread

* Re: [RFC] Split php package into php7 and php8
  2021-06-27 11:31 [ISSUE] [RFC] Split php package into php7 and php8 the-eater
                   ` (4 preceding siblings ...)
  2021-06-28 16:17 ` Duncaen
@ 2021-06-28 16:19 ` the-eater
  2021-06-28 16:26 ` Duncaen
                   ` (14 subsequent siblings)
  20 siblings, 0 replies; 22+ messages in thread
From: the-eater @ 2021-06-28 16:19 UTC (permalink / raw)
  To: ml

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

New comment by the-eater on void-packages repository

https://github.com/void-linux/void-packages/issues/31678#issuecomment-869822168

Comment:
> With configuration files if they are changed xbps won't delete the configuration file and therefor won't be able to delete the directory. xbps would not error out because it currently does not take alternatives into account for file checks.

you're gonna want to kill me but, 
that's something quite easily resolved in a INSTALL script right? 

^ permalink raw reply	[flat|nested] 22+ messages in thread

* Re: [RFC] Split php package into php7 and php8
  2021-06-27 11:31 [ISSUE] [RFC] Split php package into php7 and php8 the-eater
                   ` (5 preceding siblings ...)
  2021-06-28 16:19 ` the-eater
@ 2021-06-28 16:26 ` Duncaen
  2021-06-28 16:27 ` Duncaen
                   ` (13 subsequent siblings)
  20 siblings, 0 replies; 22+ messages in thread
From: Duncaen @ 2021-06-28 16:26 UTC (permalink / raw)
  To: ml

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

New comment by Duncaen on void-packages repository

https://github.com/void-linux/void-packages/issues/31678#issuecomment-869827732

Comment:
Thats tricky, not exactly sure how it would behave, if you move it in pre-INSTALL into a place where xbps did not consider the file previously as configuration file and then might just overwrite it.

https://github.com/void-linux/xbps/blob/4a5eb8dc87cf08ad919ec6602ef5a70e8514710c/lib/package_config_files.c#L127

^ permalink raw reply	[flat|nested] 22+ messages in thread

* Re: [RFC] Split php package into php7 and php8
  2021-06-27 11:31 [ISSUE] [RFC] Split php package into php7 and php8 the-eater
                   ` (6 preceding siblings ...)
  2021-06-28 16:26 ` Duncaen
@ 2021-06-28 16:27 ` Duncaen
  2021-06-28 16:28 ` Duncaen
                   ` (12 subsequent siblings)
  20 siblings, 0 replies; 22+ messages in thread
From: Duncaen @ 2021-06-28 16:27 UTC (permalink / raw)
  To: ml

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

New comment by Duncaen on void-packages repository

https://github.com/void-linux/void-packages/issues/31678#issuecomment-869827732

Comment:
Thats tricky, not exactly sure how it would behave, if you move it in pre-INSTALL into a place where xbps did not consider the file previously as configuration file then it might just overwrite it.

https://github.com/void-linux/xbps/blob/4a5eb8dc87cf08ad919ec6602ef5a70e8514710c/lib/package_config_files.c#L127

^ permalink raw reply	[flat|nested] 22+ messages in thread

* Re: [RFC] Split php package into php7 and php8
  2021-06-27 11:31 [ISSUE] [RFC] Split php package into php7 and php8 the-eater
                   ` (7 preceding siblings ...)
  2021-06-28 16:27 ` Duncaen
@ 2021-06-28 16:28 ` Duncaen
  2021-06-28 16:49 ` Chocimier
                   ` (11 subsequent siblings)
  20 siblings, 0 replies; 22+ messages in thread
From: Duncaen @ 2021-06-28 16:28 UTC (permalink / raw)
  To: ml

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

New comment by Duncaen on void-packages repository

https://github.com/void-linux/void-packages/issues/31678#issuecomment-869827732

Comment:
Thats tricky, not exactly sure how it would behave, if you move it in pre-INSTALL into a place where xbps did not consider the file previously as configuration file then it might just overwrite it.

https://github.com/void-linux/xbps/blob/4a5eb8dc87cf08ad919ec6602ef5a70e8514710c/lib/package_config_files.c#L127

or maybe this codepath, as you would also rename the package, in which case it would work:

https://github.com/void-linux/xbps/blob/4a5eb8dc87cf08ad919ec6602ef5a70e8514710c/lib/package_config_files.c#L92

^ permalink raw reply	[flat|nested] 22+ messages in thread

* Re: [RFC] Split php package into php7 and php8
  2021-06-27 11:31 [ISSUE] [RFC] Split php package into php7 and php8 the-eater
                   ` (8 preceding siblings ...)
  2021-06-28 16:28 ` Duncaen
@ 2021-06-28 16:49 ` Chocimier
  2021-06-28 16:56 ` the-eater
                   ` (10 subsequent siblings)
  20 siblings, 0 replies; 22+ messages in thread
From: Chocimier @ 2021-06-28 16:49 UTC (permalink / raw)
  To: ml

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

New comment by Chocimier on void-packages repository

https://github.com/void-linux/void-packages/issues/31678#issuecomment-869843030

Comment:
What usage scenarios are targeted?

Running at most one php at same time?
Running both at same time with same config file (looks limiting, as there are include_path and extension_dir there)?
Running both at same time with different config files? 

^ permalink raw reply	[flat|nested] 22+ messages in thread

* Re: [RFC] Split php package into php7 and php8
  2021-06-27 11:31 [ISSUE] [RFC] Split php package into php7 and php8 the-eater
                   ` (9 preceding siblings ...)
  2021-06-28 16:49 ` Chocimier
@ 2021-06-28 16:56 ` the-eater
  2021-06-28 16:57 ` the-eater
                   ` (9 subsequent siblings)
  20 siblings, 0 replies; 22+ messages in thread
From: the-eater @ 2021-06-28 16:56 UTC (permalink / raw)
  To: ml

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

New comment by the-eater on void-packages repository

https://github.com/void-linux/void-packages/issues/31678#issuecomment-869848391

Comment:
:heavy_check_mark: Running at most one php at same time?
:heavy_multiplication_x: Running both at same time with same config file (looks limiting, as there are include_path and extension_dir there)?
:heavy_check_mark: Running both at same time with different config files?

running both at the same time with same config file would cause issues

There's case you want to run php7 and php8 alongside when e.g. developing for a platform that hasn't migrated yet to php8

^ permalink raw reply	[flat|nested] 22+ messages in thread

* Re: [RFC] Split php package into php7 and php8
  2021-06-27 11:31 [ISSUE] [RFC] Split php package into php7 and php8 the-eater
                   ` (10 preceding siblings ...)
  2021-06-28 16:56 ` the-eater
@ 2021-06-28 16:57 ` the-eater
  2021-07-13  0:10 ` jonagoldman
                   ` (8 subsequent siblings)
  20 siblings, 0 replies; 22+ messages in thread
From: the-eater @ 2021-06-28 16:57 UTC (permalink / raw)
  To: ml

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

New comment by the-eater on void-packages repository

https://github.com/void-linux/void-packages/issues/31678#issuecomment-869848391

Comment:
:heavy_multiplication_x: Running at most one php at same time?
:heavy_multiplication_x: Running both at same time with same config file (looks limiting, as there are include_path and extension_dir there)?
:heavy_check_mark: Running both at same time with different config files?

running both at the same time with same config file would cause issues

There's case you want to run php7 and php8 alongside when e.g. developing for a platform that hasn't migrated yet to php8

^ permalink raw reply	[flat|nested] 22+ messages in thread

* Re: [RFC] Split php package into php7 and php8
  2021-06-27 11:31 [ISSUE] [RFC] Split php package into php7 and php8 the-eater
                   ` (11 preceding siblings ...)
  2021-06-28 16:57 ` the-eater
@ 2021-07-13  0:10 ` jonagoldman
  2021-08-05 16:14 ` MrFastDie
                   ` (7 subsequent siblings)
  20 siblings, 0 replies; 22+ messages in thread
From: jonagoldman @ 2021-07-13  0:10 UTC (permalink / raw)
  To: ml

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

New comment by jonagoldman on void-packages repository

https://github.com/void-linux/void-packages/issues/31678#issuecomment-878679294

Comment:
Any hope to get this merged? 
I have being building PHP 8.0 from source since its release (November 2020) but always struggled to get a perfect build.
Version 8.1 is coming soon and would love to finally have at least version 8.0 straight from Void.
Thanks. 

^ permalink raw reply	[flat|nested] 22+ messages in thread

* Re: [RFC] Split php package into php7 and php8
  2021-06-27 11:31 [ISSUE] [RFC] Split php package into php7 and php8 the-eater
                   ` (12 preceding siblings ...)
  2021-07-13  0:10 ` jonagoldman
@ 2021-08-05 16:14 ` MrFastDie
  2021-08-05 23:51 ` jchook
                   ` (6 subsequent siblings)
  20 siblings, 0 replies; 22+ messages in thread
From: MrFastDie @ 2021-08-05 16:14 UTC (permalink / raw)
  To: ml

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

New comment by MrFastDie on void-packages repository

https://github.com/void-linux/void-packages/issues/31678#issuecomment-893585604

Comment:
Same for me. I work on a daily basis with PHP and I would love to get this in the repositories. Are there any hopes for it to happen?

^ permalink raw reply	[flat|nested] 22+ messages in thread

* Re: [RFC] Split php package into php7 and php8
  2021-06-27 11:31 [ISSUE] [RFC] Split php package into php7 and php8 the-eater
                   ` (13 preceding siblings ...)
  2021-08-05 16:14 ` MrFastDie
@ 2021-08-05 23:51 ` jchook
  2021-10-08 16:52 ` Chocimier
                   ` (5 subsequent siblings)
  20 siblings, 0 replies; 22+ messages in thread
From: jchook @ 2021-08-05 23:51 UTC (permalink / raw)
  To: ml

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

New comment by jchook on void-packages repository

https://github.com/void-linux/void-packages/issues/31678#issuecomment-893899400

Comment:
> Before I do any of this I would like some feedback if this the correct way forward or if there's a better way to do so

You could publish a separate PHP repository, e.g. structured similar to [Ondřej Surý's](https://deb.sury.org/).

Then the main void-packages repository can keep it simple, ideally updating to PHP 8.x before [28 Nov 2021](https://www.php.net/supported-versions.php).

^ permalink raw reply	[flat|nested] 22+ messages in thread

* Re: [RFC] Split php package into php7 and php8
  2021-06-27 11:31 [ISSUE] [RFC] Split php package into php7 and php8 the-eater
                   ` (14 preceding siblings ...)
  2021-08-05 23:51 ` jchook
@ 2021-10-08 16:52 ` Chocimier
  2021-12-18  2:21 ` jchook
                   ` (4 subsequent siblings)
  20 siblings, 0 replies; 22+ messages in thread
From: Chocimier @ 2021-10-08 16:52 UTC (permalink / raw)
  To: ml

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

New comment by Chocimier on void-packages repository

https://github.com/void-linux/void-packages/issues/31678#issuecomment-938845859

Comment:
So my point was that if different series will read different config files (and they have to for running many at same time), there is little value in introducing alternative pointing to "current" series config.

^ permalink raw reply	[flat|nested] 22+ messages in thread

* Re: [RFC] Split php package into php7 and php8
  2021-06-27 11:31 [ISSUE] [RFC] Split php package into php7 and php8 the-eater
                   ` (15 preceding siblings ...)
  2021-10-08 16:52 ` Chocimier
@ 2021-12-18  2:21 ` jchook
  2021-12-18  2:25 ` jchook
                   ` (3 subsequent siblings)
  20 siblings, 0 replies; 22+ messages in thread
From: jchook @ 2021-12-18  2:21 UTC (permalink / raw)
  To: ml

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

New comment by jchook on void-packages repository

https://github.com/void-linux/void-packages/issues/31678#issuecomment-997126902

Comment:
Note PHP 7 will be EOL in less than a year from now

^ permalink raw reply	[flat|nested] 22+ messages in thread

* Re: [RFC] Split php package into php7 and php8
  2021-06-27 11:31 [ISSUE] [RFC] Split php package into php7 and php8 the-eater
                   ` (16 preceding siblings ...)
  2021-12-18  2:21 ` jchook
@ 2021-12-18  2:25 ` jchook
  2021-12-18  2:26 ` jchook
                   ` (2 subsequent siblings)
  20 siblings, 0 replies; 22+ messages in thread
From: jchook @ 2021-12-18  2:25 UTC (permalink / raw)
  To: ml

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

New comment by jchook on void-packages repository

https://github.com/void-linux/void-packages/issues/31678#issuecomment-997126902

Comment:
Note PHP 7 will be EOL in less than a year from now. 

If it takes 6 months to decide whether to go ahead, maybe it's better to focus on updating to PHP 8 and let PHP 7 folks lock-in their version.

^ permalink raw reply	[flat|nested] 22+ messages in thread

* Re: [RFC] Split php package into php7 and php8
  2021-06-27 11:31 [ISSUE] [RFC] Split php package into php7 and php8 the-eater
                   ` (17 preceding siblings ...)
  2021-12-18  2:25 ` jchook
@ 2021-12-18  2:26 ` jchook
  2022-02-04 14:19 ` TinfoilSubmarine
  2022-04-29 10:33 ` [ISSUE] [CLOSED] " paper42
  20 siblings, 0 replies; 22+ messages in thread
From: jchook @ 2021-12-18  2:26 UTC (permalink / raw)
  To: ml

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

New comment by jchook on void-packages repository

https://github.com/void-linux/void-packages/issues/31678#issuecomment-997126902

Comment:
Note PHP 7 will be EOL in less than a year from now.

^ permalink raw reply	[flat|nested] 22+ messages in thread

* Re: [RFC] Split php package into php7 and php8
  2021-06-27 11:31 [ISSUE] [RFC] Split php package into php7 and php8 the-eater
                   ` (18 preceding siblings ...)
  2021-12-18  2:26 ` jchook
@ 2022-02-04 14:19 ` TinfoilSubmarine
  2022-04-29 10:33 ` [ISSUE] [CLOSED] " paper42
  20 siblings, 0 replies; 22+ messages in thread
From: TinfoilSubmarine @ 2022-02-04 14:19 UTC (permalink / raw)
  To: ml

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

New comment by TinfoilSubmarine on void-packages repository

https://github.com/void-linux/void-packages/issues/31678#issuecomment-1030031695

Comment:
Has there been any progress on this? I'd like to help out with this if anything is needed. I had a PHP app that required 8.0 so I manually updated the needed packages and am using them successfully.

^ permalink raw reply	[flat|nested] 22+ messages in thread

* Re: [ISSUE] [CLOSED] [RFC] Split php package into php7 and php8
  2021-06-27 11:31 [ISSUE] [RFC] Split php package into php7 and php8 the-eater
                   ` (19 preceding siblings ...)
  2022-02-04 14:19 ` TinfoilSubmarine
@ 2022-04-29 10:33 ` paper42
  20 siblings, 0 replies; 22+ messages in thread
From: paper42 @ 2022-04-29 10:33 UTC (permalink / raw)
  To: ml

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

Closed issue by the-eater on void-packages repository

https://github.com/void-linux/void-packages/issues/31678

Description:
Currently we only provide one leading php version which is currently pinned at php 7.4 (the latest supported version of php 7)

this has generally not been a problem since the migration from php 5.6 to php 7.0 was rather painless, however with php 8 this is not as painless and because of new features and changes in behavior loads of projects may or will be broken.

but php 8 is currently the leading version (and also i want to play with it) and waiting for adoption seems a bit misguided and annoying for everyone (me) wanting to adopt php 8.

To resolve this situation I am proposing the following

- [ ] Move `php` to `php7`
- [ ] Create xbps-alternatives group for php which symlinks the correct folders and binaries
- [ ] Create new `php8` package
- [ ] Copy and move all php extensions to `php7` and `php8` prefixed packages (these are `xdebug`, `php-apcu`, `php-ast`, `php-igbinary` and `php-imagick`)
- [ ] Provide a wrapper script for `pecl` (from the new `pear` package) (`pecl7` and `pecl8`) which sets the correct program suffix for compiling pecl extensions

both php versions will have matching postfixes e.g. `php7` will provide `php7` and it's config files will live in `/etc/php7` etc.

If we do migration of `php` -> `php7` correctly there should be no conflicts, we can move the `/etc/php` to `/etc/php7` directory if present.

php packages directly affected:

`phpMyAdmin` and `ampache`: DIY hosting package, so can be kept an exercise to the reader
`phoronix-test-suite`: We need to check for php8 support, if there is none we can pin and patch it to use php7
`composer`: Works on both php7 and php8 so can be kept as is
`pear` (replaces php-pear): Works on both php7 and php8 and can be mostly kept as is except the pecl part, which is explained in my TODO list
`php-*`: Are all bundled extensions with the exception of the items listed above, but these can all be migrated alike php
`xdebug`: Non-bundled extension but can me migrated alike the other extensions

Before I do any of this I would like some feedback if this the correct way forward or if there's a better way to do so

/cc @paper42 (because you raised this issue)

Fuck I am basically back at doing the shit I did at my first job

^ permalink raw reply	[flat|nested] 22+ messages in thread

end of thread, other threads:[~2022-04-29 10:33 UTC | newest]

Thread overview: 22+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-06-27 11:31 [ISSUE] [RFC] Split php package into php7 and php8 the-eater
2021-06-28 16:05 ` Chocimier
2021-06-28 16:08 ` the-eater
2021-06-28 16:14 ` the-eater
2021-06-28 16:16 ` Duncaen
2021-06-28 16:17 ` Duncaen
2021-06-28 16:19 ` the-eater
2021-06-28 16:26 ` Duncaen
2021-06-28 16:27 ` Duncaen
2021-06-28 16:28 ` Duncaen
2021-06-28 16:49 ` Chocimier
2021-06-28 16:56 ` the-eater
2021-06-28 16:57 ` the-eater
2021-07-13  0:10 ` jonagoldman
2021-08-05 16:14 ` MrFastDie
2021-08-05 23:51 ` jchook
2021-10-08 16:52 ` Chocimier
2021-12-18  2:21 ` jchook
2021-12-18  2:25 ` jchook
2021-12-18  2:26 ` jchook
2022-02-04 14:19 ` TinfoilSubmarine
2022-04-29 10:33 ` [ISSUE] [CLOSED] " paper42

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).