Bug 216366
Summary: | RFE: Please include MySQL support within PHP | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Tom Wood <woodt> |
Component: | comps | Assignee: | David Cantrell <dcantrell> |
Status: | CLOSED RAWHIDE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6 | CC: | jorton |
Target Milestone: | --- | Keywords: | Reopened |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-01-04 16:34:31 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Tom Wood
2006-11-20 00:03:04 UTC
Can comps be changed to ensure that for whatever package group selects php, php-mysql is also selected by default? This is undoubtedly the most common user complaint we get for PHP. Thank you, Joe. That's the exact response and fix that I was hoping to see championed. This is the most common complaint that I get about from my clients about PHP as well. took this by accident Without making a change to the package itself, or making a "php" group, no. It's optional in both the Mysql group, and in the webserver group. If we made this assumption for mysql, we'd have to make it for postgresql, and odbc, and any other DB type that might crop up. So it's not possible to have php-mysql enabled by default in the "Web Server" group? Why would we have to do the same for pgsql etc if this is done for php-mysql? (In reply to comment #5) > So it's not possible to have php-mysql enabled by default in the "Web Server" group? Yes, it could be enabled in the Web Server group, but now you're assuming that every person who wants a webserver ALSO wants php, AND mysql, which is not a valid assumption. > Why would we have to do the same for pgsql etc if this is done for php-mysql? What makes mysql special? If we automatically installed mysql, we'll get the same request to have postgres automatically installed too for those users. I'd rather not play favorites and let people chose whatever they want. Of course we play favourites both in the set of packages we chose to ship and those we chose to install by default. The "Web server" group plays favourites and selects PHP and not Tomcat by default. It should also play favourites and install php-mysql. The most common user request/complaint/confusion we see around the web server is exactly "why doesn't MySQL work in PHP". Not PostgreSQL and not UnixODBC. If it is technically possible then installing php-mysql by default for the "web server" group is certainly the right thing to do. To that extent, with the new way we'll be doing Fedora, targetted spins of the package set that is both core/extras combined, when we do a "server" spin, should we even include the pgsql/odbc? They would be available if you enabled the network and access to the big repo of packages, but should they be included in the media we spin? I'll make the change for now in our comps, but this question will need to be answered for Test1. I still don't like the fact that now we're shoving mysql down the throat of anybody who wants a webserver. |