Closed judfs closed 11 months ago
Guilty of putting it under debian just because that is what I was using. I have no opinions on how the documentation should be presented. A general configuration trouble shooting section might be useful in the build document?
I don't know if its a normal thing to use as a base, but turns out the official python docker images have multiple pythons installed.
I'll leave it to the maintainers to figure out what fits best then.
I think that a new section in the build instructions document makes sense. Maybe Troubleshooting
, Errata
, Helpful Hints
or something like that?
Uhh oops. I synced my master and closed this discussion. My original suggested changes were moved to https://github.com/judfs/lcm/tree/doc-notes .
Documenting a build case I ran into when trying to build an image starting with
FROM python:3.11-bullseye