Mention Fedora/EPEL package and installable testsuite in the Wiki
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.7k
- Forks
- 662
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 2
Description
I couldn't find a way to make a PR for the Wiki so I'm writing it here. Feel free to provide suggestions or edits.
Location: Above "RHEL7 with EPEL requires installing python36-pexpect and running cmake3."
You can also install the testsuite by passing the -DINSTALL_TESTSUITE=ON option to cmake.
Location: Below "You can force Eclipse to rebuild the project by pressing Ctrl-B."
You can also install rr and rr-testsuite directly from the Fedora and EPEL repositories:
sudo yum install rr rr-testsuite
Location: At the very bottom.
If you installed the testsuite using the -DINSTALL_TESTSUITE=ON option or rr-testsuite (Fedora/EPEL), the testsuite will be located at $libdir/rr/testsuite. To run the testsuite:
cd $libdir/rr/testsuite/obj
ctest
Note: There are some test cases which do not work correctly when ran from the installable testsuite.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Open the Wiki and locate the three positions identified in the issue: above the RHEL7/EPEL note, below the Eclipse rebuild note, and at the bottom. Add the Fedora/EPEL package command, the -DINSTALL_TESTSUITE=ON installation and ctest instructions, and the note about unsupported installed-testsuite cases; done means all requested guidance is present.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cmake
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 48/100