expands information for local compilations, clarify not all recipes builds #125
Conversation
…ill build * helps and closes nodejs#123 due a rare error like `ccache: error: Could not find compiler "g++" in PATH`
| rm -fr ~/Devel/unofficial-builds-home | ||
| mkdir -p ~/Devel/unofficial-builds-home | ||
| cd ~/Devel/unofficial-builds-home |
There was a problem hiding this comment.
I think you should ditch the ~/Deve/ prefixes here, let the user do it in cwd or edit this themselves.
There was a problem hiding this comment.
I did to avoid mixed files in home, most of users works not so organized .. we must promoted organization but i dont know how to promoted such thing.. what do you suggest? this allows people to know easyle that all related files is under that path only
There was a problem hiding this comment.
in fact @rvagg the command with such prefixed helps to understand to others (that are not English native speakers) the confusion of "homedir"
There was a problem hiding this comment.
yeah, fair enough and you have documented it below that this is what you're doing. What stands out to me is "Devel" though, it's not a standard thing, looks macOSish, and the user is inevitably going to have to edit that. So maybe just ditch the "/Devel" from your commands and run with ~/unofficial-builds-home.
There was a problem hiding this comment.
ok b eore changin.. as last attempt to defend my point, it is not a macshish but just like this Downloads, and like XDG in linux has Public or Music several subdirectories, in the original text i thought thinked i was forced to use home directly since due to language barriers you always think that it is understood very well, but the examples are essential, if even with this explanation I cannot convince you then I change it as you suggest, but i am here cos many others just get tyred of put issues with questions that canot xperess in good way.. developers always thnks have reason but we are first humans.. that's why i put later $workdir will be ~/Devel/unofficial-builds-home
nodejs#125 (review) Co-authored-by: Rod Vagg <rod@vagg.org>
…tions nodejs#125 (review) yes, sorry, mabe was better "recipe & versions combinations" but well.. we already address that in nodejs#123 Co-authored-by: Rod Vagg <rod@vagg.org>
Co-authored-by: Rod Vagg <rod@vagg.org>
|
ok, I don't think I care enough about the |
sorry about the large explanation.. i now will make some packages around your helps! i hope some people understand the adition and feel free to change it if does not help 👍 |
This little change in the README.md helps and closes #123 due a rare error like
ccache: error: Could not find compiler "g++" in PATH.. instructions was improved for non familiar with nodejs build processAditional, apparently not all recipes compile in all flavors, I have noticed, for example, that in 16.x.y they only compile some while in 20.x.y they compile almost all of them. i noted this also in the alredy released tarball, by example https://unofficial-builds.nodejs.org/download/release/v20.11.1/ already have almost all recipes .. but for https://unofficial-builds.nodejs.org/download/release/v16.20.2/ i noted there is not x64-glibc-217 recipe released..