docs: add explanation for the build and how-to for build passthroughs#504
Conversation
tang-mm
left a comment
There was a problem hiding this comment.
Nice write-up and thanks for documenting the solution! My main suggestion is to clearly state eligibility upfront (as much as we know) to prevent potential build failures in legacy or specialized environments
dwilding
left a comment
There was a problem hiding this comment.
Changes look great, thanks! On this reading, I spotted a potential issue related to pip version. I'm sorry, I missed this the first time I was looking at the Makefile.
dwilding
left a comment
There was a problem hiding this comment.
A couple of minor suggestions - but overall I really like the updated structure and explanations. Nice one!
|
@dwilding @a-velasco @tang-mm @akcano Thanks so much for your reviews! You've helped make this a much better doc. I'm going to PR this against main, so some force-pushes are incoming. |
`VALEDIR` represents the package directory for Vale, yet it re-establishes the same path as `VENVDIR`. It makes more sense to compose it from `VENVDIR`. Furthermore, since `VENVDIR` is configurable by the calling environment, it stands to reason that `VALEDIR` should be, too.
f1a8f7f to
34a64cb
Compare
All comments addressed, GitHub is being difficult.
This is the companion document to #494.
- [ ] Have you updatedCHANGELOG.mdwith relevant non-documentation file changes?