-
Notifications
You must be signed in to change notification settings - Fork 10
php73 #219
Comments
Thanks for the request @Xon, I'll take a look at this as soon as I'm able. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Sorry for the delay here. I don't want to make excuses here, but I'd like to share some context that has contributed to this and other new package requests not being completed yet. The history of the IUS project has resulted in many parts of the build process being locked behind the Rackspace corporate firewall. This has hampered the ability of the project to grow and take on non-Rackspace contributors. I've been working on changing that for some time now. I'm heavily focused on modernizing and revamping the infrastructure to be more sustainable and enable more community participation. It has taken longer than anyone wanted, but there is light at the end of the tunnel. Stay tuned for more news on this front by subscribing to iuscommunity/announce. Until then, there are still ways to get involved. Fulfilling new package requests is important, but so is keeping the current packages up to date. Often times I'll have to drop my infrastructure work to update existing packages, especially when the upstream release contains security fixes. If you notice an existing package you use that has fallen behind the upstream, please open an issue on the package source repo (found in the @iuscommunity-pkg organization) to bring it to my attention, especially if the upstream release contains security fixes. For example, @snlnspc was kind enough to let me know httpd24u was outdated, and the upstream 2.4.39 contained security fixes, so I was able to change focus and get an update out. To take it to the next level, take a shot at updating the spec file yourself and sending a pull request. The commit history on each repo is full of examples of what these updates typically look like. Often times it's as simple as changing the version and adding a changelog entry. Here's an example where @sethryder updated the php72u spec file. Here's another example where @rosset took care of tmux2u. Sometimes patches will need to be rebased on the latest source code or removed entirely if they no longer apply. This was the case when @smokris wanted to help update mariadb101u. If you do send a pull request, try to build it locally in mock first, and indicate in the pull request if this was successful. Even if the build fails, reporting the error message will help me zero in on the fix, and we can work it into the pull request as additional commits. I've also been working on adding more documentation to help onboard new contributors. Checkout the packaging guidelines and the walkthrough of creating a new IUS package. Over time I hope to move more of the website content to GitHub wiki pages. If you like technical writing, this is another area where I could use assistance. Once I've got the IUS website content trimmed down a bit I'd like to switch it from web servers to GitHub pages. I'm usually available in the |
Looks good so far! |
I now have a couple of developers VM with those packages, and the internal test server, So far so good. |
I noticed the packages for php 7.3 does not have the traditional u in the name. Sample:
|
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
@agarzon You are correct, we chose to name the PHP 7.3 packages php73 instead of php73u. The background of the "u" suffix is explained here. Red Hat now prefixes all their software collections with the "rh-" prefix, so our "u" suffix is no longer necessary. Regarding the PECL redis module, allow me to level set expectations. In order to best allocate our limited resources, we do not automatically carry forward modules from one package branch to another. Every IUS packages exists because someone requested it. As @rossnick pointed out, the redis module has been requested for php73 in #230, and I've just published it to the testing repo if you want to start using it. If there is PECL module that we packaged for an earlier PHP that we haven't (yet) packaged for php73, just open a wishlist request for it and we'll see if we can accommodate it. |
What new package do you want?
php 7.3
Why?
Latest stable php release. (06 Dec 2018 release)
Testing
I agree to test the new package to ensure that it works as expected. Once I am
satisfied with the results of my testing I will comment on this issue with the
word "STABLE" to get it promoted to the stable repos.
The text was updated successfully, but these errors were encountered: