Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add new Build Prerequisites page #31

Closed
wants to merge 3 commits into from

Conversation

hauten
Copy link
Contributor

@hauten hauten commented Mar 20, 2020

Three commits involved in copying content from http://flux-framework.org/docs/requirements/ into a new .rst file for this repo. Preview isn't working for me in VS, so please let me know if I need to make any formatting corrections. Resolves the last task on flux-framework/flux-framework.github.io#36. Closes: #36

Copy link
Member

@SteVwonder SteVwonder left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @hauten! Few inline suggestions below but other than that, LGTM!

+-------------+----------+--------------------------+
| Requirement | Version | Notes |
+=============+==========+==========================+
| `libsoduim` | `>1.0.1` | |
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
| `libsoduim` | `>1.0.1` | |
| `libsodium` | `>1.0.1` | |

Lua
---

Flux makes use of Lua scripts and bindings for some functionality. Lua 5.1 is required for now. However, support for v5.2 and v5.3 is planned in the near future.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The original source material was out-of-date. Sorry about that.

Suggested change
Flux makes use of Lua scripts and bindings for some functionality. Lua 5.1 is required for now. However, support for v5.2 and v5.3 is planned in the near future.
Flux makes use of Lua scripts and bindings for some functionality. Lua 5.1 or 5.2 are required.

+-------------+----------+--------------------------+
| Requirement | Version | Notes |
+=============+==========+==========================+
| `python` | `>=2.7` | |
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We just recently went python 3.6+. 🎆

Suggested change
| `python` | `>=2.7` | |
| `python` | `>=3.6` | |

+-------------+----------+--------------------------+
| `pycparser` | `>=2.2` | |
+-------------+----------+--------------------------+
| `ply` | `>=3.6` | |
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmmmm. I don't think I've ever seen this dependency. @trws did this used to be a dependency for the bindings at some point in time? I don't think it is anymore, right? Same for pycparser? We don't explicitly depend on it but transitively do through cffi?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we also have dependencies on jsonschema and yaml. But that can be a separate PR.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, we have explicit dependencies on jsonschema and yaml, which we should really provide a requirements.txt for or similar I suppose. I think ply is used by pycparser, and pycparser by cffi. We currently do not directly depend on pycparser, but we might soon as it looks like it might be a promising way to do some fixing in the binding generation I mentioned not too long ago.

@SteVwonder
Copy link
Member

Preview isn't working for me in VS, so please let me know if I need to make any formatting corrections.

FWIW, if you go to the bottom of the PR, click "Show all check", then click "Details" for the read-the-docs check, it should bring you to a live view of the PR, built by RTD.

@vsoch
Copy link
Member

vsoch commented Mar 2, 2023

@hauten are you still interested in contributing this? It might be hard to maintain given how quickly dependencies and versions change. If you want to drop the PR, I think that would be OK, but if you want to pick it back up, I think we could have a link under "Manual Installation." https://flux-framework.readthedocs.io/en/latest/quickstart.html#manual-installation

The reason to put it there is because anyone doing the docker install doesn't care about building (they get it ready to go in a container) and the spack install will always keep updated dependencies. If we do have this list, I'm wondering if we would want to just list the general dependencies without pinning versions, and use the sections to primarily describe how each is used. It would be a "did you know" for the advanced / interested developer (if I had to scope the goal of listing them).

If we want to direct a reader that is looking for an actual set of "the current deps and versions to install" we probably want to point to a file in GitHub that is doing the building (and regularly updated) and not have to maintain that information in two places.

@hauten
Copy link
Contributor Author

hauten commented Mar 2, 2023

@hauten are you still interested in contributing this? It might be hard to maintain given how quickly dependencies and versions change. If you want to drop the PR, I think that would be OK, but if you want to pick it back up, I think we could have a link under "Manual Installation." https://flux-framework.readthedocs.io/en/latest/quickstart.html#manual-installation

The reason to put it there is because anyone doing the docker install doesn't care about building (they get it ready to go in a container) and the spack install will always keep updated dependencies. If we do have this list, I'm wondering if we would want to just list the general dependencies without pinning versions, and use the sections to primarily describe how each is used. It would be a "did you know" for the advanced / interested developer (if I had to scope the goal of listing them).

If we want to direct a reader that is looking for an actual set of "the current deps and versions to install" we probably want to point to a file in GitHub that is doing the building (and regularly updated) and not have to maintain that information in two places.

This is from the effort to move the original docs into Sphinx/RtD; I was involved only in the initial migration, not maintenance since then. I agree that keeping it updated with various versions is onerous, and I'm sure Flux has changed a lot in the time since. Feels like an obsolete PR.

@vsoch
Copy link
Member

vsoch commented Mar 2, 2023

Ok thanks for the update (and you are a hero for doing that! 🙌) let’s close the PR then.

@vsoch vsoch closed this Mar 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

docker: include instructions for starting munge
4 participants