HI all,

I was just wondering how the rest of the EPEL community felt in this area and if perhaps teh EPEL Steering Committee might want to review policies surrounding SCL use.

There's a growing need for more modern language versions in the EL world.

I've only just encountered this situation in carrying out packaging updates for OwnCloud in EPEL but I'm sure many others have encountered similar situations - it's been one of the issues in Let's Encrypt for EPEL6 as an example.

In the specific instance I've encountered OwnCloud needs to be retired from EPEL6 due to the PHP version there being only 5.3, with a minimal of 5.4 needed.

If the SCL php54 or php55 was accessible then we could have continued supporting our users there.

Even on the most recent Red Hat Enterprise Linux 7 release it's now php54 which is already EOL upstream and although OwnCloud itself supports 5.4+ there's some apps (gallery+ for instance) that requires php55+.

The oC documentation even has a big section on enabling SCL php55 in EL7

https://doc.owncloud.org/server/9.0/admin_manual/installation/php_55_installation.html

I fear that with SCL now here there won't be any rebasing or parallel packaging in the EL7 lifespan (many years yet to go) with an increased reliance on SCL by RH for RHEL which will impact the ability of the EPEL maintainers to deliver repo packaged products to our users.

How do others feel and does the Steering Committee feel it might be time to revisit the SCL question?

Cheers,

JAmes