-
Notifications
You must be signed in to change notification settings - Fork 50
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
instalation path routes #122
Comments
Run |
umm thanks.. so were forced to use /usr/local then |
not quite, it's just how it's landed here and nobody thought to change it, perhaps we could migrate here and change all our recipes? I think that's probably best done on a major version bump, so we'd have to maintain some branching around that version but then we could I personally prefer /usr/local so this suits me, but it doesn't bother me too much so you're welcome to propose it if you feel like coding that up for all the recipes. |
fwiw I did remember to set this in the snaps, so they default to there's precedent at least I think the binaries from nodejs.org though use /usr/local, so maybe that's a stronger precedent? |
well /usr/local its default unix philosophy ! i asking only cos i was planning to package into deb/rpm but seems will not work with such prefix so i will plan to build for older distributions.. most people said shit about "nobody uses x version" but that's lie.. its few ones but the world is huge .. and still there are people here using older releases and older devices |
yep, I agree and I've tried to lean toward the extended support model of this, but the tail is very very long and sometimes you have to draw a line somewhere just for the sake of combinatorial explosiveness |
i will try to package it for older debian and alpine releases.. thanks for your support and i'll tyry to help as i can to this repo |
hi, i checked and try to build by myselft but in script but despicte error of #123 i note the argument passed to python "--prefix=/" in log (check issue referenced) |
Yeah, you're right about that, so this took me down a rabbit hole but it looks like we've never been able to use So, I think what you're going to need to do is separately |
i was able to build using /usr prefix.. but README was not so clear.. i made a PR about this! chek it! |
@rvagg you must open this again.. i checked the log of compilation and prefix do not honors in local or remote builds, relevant part is posted : noted the part :
|
ok solve it, you cannot reuse the dockers layers.. all dockers must be prube.. i already put it on the pull request that as note.. not as step |
the README and files does not details if the nodejs program will search for modules in "/usr/lib" or "./lib" or what tripled, any info of this?
this is to difference system installed modules and user only installed modules
The text was updated successfully, but these errors were encountered: