How to check prerequisites before installing kinto?
- Dominant language
- Python
- Stars
- 4.4k
- Forks
- 437
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 15
Description
Depends on the platform, *kinto* needs to be satisfied by prerequisites such as *python* in the first place with the major version 3 and the minor version greater than or equals to 6 as well as some specific libraries like *libffi* and so on, existing scripts in which check prerequisites could be very helpful. For instance, `kinto.cmd` runs in _MS-Windows_ command prompt and `kinto.sh` can be executed via terminals in _Unix-based_ operating systems. It helps the whole process will be **automated**.
A simple report generated by each of which script can be like the following lines:
|OS Name|OS Major Version|
|:---|:---:|
|`Microsoft Windows 10 Enterprise LTSC`|10|
|Required|Installed|
|:---|:---:|
|Python|3.7|
|GCC|4.9|
|pip|19.3|
|make|4.3|
|nmake|15.0|
|cmake|N/A|
|...|...|
Even more simple
|Wanted|Satisfied|
|:---|:---:|
|Python|ok|
|GCC|ok|
|pip|ok|
|make|ok|
|nmake|ok|
|cmake|ko|
|...|...|
This report should have listed prerequisites meanwhile it checks whether _kinto_ is satisfied to be installed or not. In such cases, there are some unsatisfied prerequisites the script has to be organized so that interact with the user to download and install the _unchecked_ item(s).
Contributor guide
Research direction
Start by locating the platform-specific kinto.cmd and kinto.sh entry points and reviewing how installation currently checks prerequisites. Define the prerequisite report for Python, GCC, pip, make, nmake, cmake, and related items, then verify the scripts identify unsatisfied requirements and interact with users about them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, shell
- Domain
- devops, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100