Bug 1401281 - README.md refers to a non-existant 'INSTALL' file
Summary: README.md refers to a non-existant 'INSTALL' file
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: vdsm
Classification: oVirt
Component: Documentation
Version: 4.18.18
Hardware: All
OS: Linux
unspecified
low
Target Milestone: ovirt-4.2.0
: 4.20.3
Assignee: Irit Goihman
QA Contact: Radim Hrazdil
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-04 09:57 UTC by Yaniv Kaul
Modified: 2017-12-20 11:31 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-12-20 11:31:50 UTC
oVirt Team: Infra
Embargoed:
rule-engine: ovirt-4.2+
rule-engine: planning_ack+
oourfali: devel_ack+
rule-engine: testing_ack+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 80856 0 master MERGED documentation: update README.md 2017-08-28 09:31:32 UTC

Description Yaniv Kaul 2016-12-04 09:57:47 UTC 
Description of problem:

In README.md, it says:
'The Vdsm service can be used by following the standard autotools
installation process, documented in the INSTALL file."

There is no INSTALL file.

Version-Release number of selected component (if applicable):
master, latest commit 1ff41b1c321665e6361efc5c6e86ad31d71eadee
Comment 1 Dan Kenigsberg 2016-12-04 10:12:37 UTC 
And even more importantly, we do not really support the standard autotools `make install`. The only tested method of installation is via RPM. So the how paragraph should be rewritten.
Comment 2 Radim Hrazdil 2017-09-04 08:30:44 UTC 
Verified documentation has been changed accordingly.
Comment 3 Sandro Bonazzola 2017-12-20 11:31:50 UTC 
This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017.

Since the problem described in this bug report should be
resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.
Note You need to log in before you can comment on or make changes to this bug.