Skip to content

Conversation

@bluegate010
Copy link

@bluegate010 bluegate010 commented Apr 22, 2025

To build:

First clone ocp-spec-tools, and then run:

$ path/to/ocp-spec-tools/docker-pull.sh
$ path/to/ocp-spec-tools/docker-run.sh --pdf OpenRMC_UsageGuide_v1.2.pdf OpenRMC_UsageGuide_v1.2.ocp

The following metadata fields are not currently respected by ocp-spec-tools:

  • supersedes
  • status
  • released
  • class
  • copyright
  • paragraph_numbering

@bluegate010 bluegate010 force-pushed the openrmc-spec-convert branch 4 times, most recently from 471fdd7 to 93f1fc8 Compare April 22, 2025 02:40
@bluegate010 bluegate010 marked this pull request as draft April 22, 2025 02:45
@bluegate010 bluegate010 force-pushed the openrmc-spec-convert branch 2 times, most recently from 9c6b15e to f631978 Compare April 23, 2025 04:46
This includes some minor spacing changes for code blocks to keep JSON on the rendered
page.

To build:

First clone [ocp-spec-tools](https://github.com/opencomputeproject/ocp-spec-tools/), and then run:

```
$ path/to/ocp-spec-tools/ocp-docker-pull.sh
$ path/to/ocp-spec-tools/ocp-docker-run.sh --pdf OpenRMC_UsageGuide_v1.2.pdf OpenRMC_UsageGuide_v1.2.ocp
```

The following metadata fields are not currently respected by ocp-spec-tools:

 - `supersedes`
 - `status`
 - `released`
 - `class`
 - `copyright`
 - `paragraph_numbering`

Signed-off-by: Jeff Andersen <jeffandersen@google.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants