[DOCS-3887] Specify dependencies for install from tar-gz file from subscription downloads Created: 11/Aug/14 Updated: 30/Oct/23 Due: 13/May/15 Resolved: 22/Jun/15 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Anil Kumar | Assignee: | Andrew Aldridge |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Days since reply: | 8 years, 34 weeks, 1 day ago | ||||||||||||||||||||
| Description |
|
Page: http://docs.mongodb.org/manual/administration/install-enterprise/ Although we provide tar-gz files for download and manual install for both RedHat / Ubuntu, we do not specify what are the needed pre-requisite packages for these installs. The same is available for SuSE and Amazon Linux since those are supported only using tar-gz downloads. We should provide the needed dependencies for all the platforms that have tar-gz downloads available. |
| Comments |
| Comment by Githook User [ 23/Jun/15 ] |
|
Author: {u'username': u'i80and', u'name': u'Andrew Aldridge', u'email': u'i80and@foxquill.com'}Message: Signed-off-by: kay <kay.kim@10gen.com> |
| Comment by Githook User [ 23/Jun/15 ] |
|
Author: {u'username': u'i80and', u'name': u'Andrew Aldridge', u'email': u'i80and@foxquill.com'}Message: Signed-off-by: kay <kay.kim@10gen.com> |
| Comment by Githook User [ 22/Jun/15 ] |
|
Author: {u'username': u'i80and', u'name': u'Andrew Aldridge', u'email': u'i80and@foxquill.com'}Message: Signed-off-by: kay <kay.kim@10gen.com> |
| Comment by Githook User [ 22/Jun/15 ] |
|
Author: {u'username': u'i80and', u'name': u'Andrew Aldridge', u'email': u'i80and@foxquill.com'}Message: Signed-off-by: kay <kay.kim@10gen.com> |
| Comment by Charlie Page [ 12/Jun/15 ] |
|
An ideal solution would be to have the docs dynamically link to a file that the build generates upon creating the RPM/ etc. This file (some plain text <dependency><cr/lf>, windows format as that is the vast majority of desktops in the world) would then
A static build list will likely end up being updated when customers open tickets about it not working. That is not an ideal update process. |