Bug #83545 | Requirements for clients not documented | ||
---|---|---|---|
Submitted: | 26 Oct 2016 10:51 | Modified: | 26 Oct 2016 19:12 |
Reporter: | Daniël van Eeden (OCA) | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Cluster: Documentation | Severity: | S3 (Non-critical) |
Version: | 7.5 | OS: | Any |
Assigned to: | MySQL Verification Team | CPU Architecture: | Any |
[26 Oct 2016 10:51]
Daniël van Eeden
[26 Oct 2016 11:54]
MySQL Verification Team
Hi, I do not think we should really document in mysql cluster documentation what each distro pack in to what repo. The RPM system properly handles the dependency resolution and it's up to system administrator to know where to find the dependencies.. in the case of MethodMaker the admin might chose to get it from EPEL but it might chose to get it from some other repo, we are not forcing any of those, just as long as MethodMaker is there. kind regards Bogdan Kecman
[26 Oct 2016 18:53]
Daniël van Eeden
Ok, but in that case shouldn't one of the installation steps be 'Install Class::MethodMaker'? Maybe just list is as a prerequisite for the installation procedure?
[26 Oct 2016 19:12]
MySQL Verification Team
Hi, I strongly disagree, as then it can be argued that you also need to have whole bunch of other libraries configured, installed the os etc etc .. It is assumed that installation is done by the system administrator (in case of RHEL/OL that's supported platform in this case) and every decent sysadmin will anyhow have EPEL installed, not to mention, will know how to install dependencies. To list "what dependencies exist" you have that all inside the RPM, don't see a point of listing them on the documentation page, and if you are going to satisfy them by turning on EPEL or some other repo, or you will install it trough CPAN and --nodeps install it is totally sysadmin's choice. take care Bogdan