You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't have sudo on my dev machines but have successfully built the dev build despite that.
Process followed:
Install the various dependencies as root
mkdir /wedge && chown $USER:$USER /wedge
sed 's_sudo__'g build/*, roughly - hacked sudo out one at a time until success
Tests pass
The key change is probably dropping sudo from sudo $0 _unboxed-install "$@" in deps/wedge.sh, may also need to patch sudo $0 _install-new-r "$@" from build/py.sh.
apt install is present in a couple of places, test/spec-bin.sh build/deps.sh and there's a release-only set involving valgrind elsewhere.
I'm not sure on the cleanest way to modify the build scripts to make this optional. Perhaps allowing /wedge to be somewhere non-root-owned and then installing as a user instead?
The text was updated successfully, but these errors were encountered:
That was a bit of silly experiment where I thought we could cache /wedge, but we couldn't cache /home/ANYUSER/wedge
But now I realize we don't really need caching for this particular problem
I also realized that the WEDGE package defs can pretty much be written so their agnostic of /home/user/wedge vs. /wedge (in case we ever want caching for a different problem)
Caches under root and not under $USER wouldn't be much of a disaster either - it's already an initial build-deps.sh step that you don't run particularly often, and it runs within the time it took to find coffee on a slow machine. I haven't looked up what wedge actually is but am glad the build didn't lead with installing docker.
I don't have sudo on my dev machines but have successfully built the dev build despite that.
Process followed:
The key change is probably dropping sudo from
sudo $0 _unboxed-install "$@"
in deps/wedge.sh, may also need to patchsudo $0 _install-new-r "$@"
from build/py.sh.apt install is present in a couple of places, test/spec-bin.sh build/deps.sh and there's a release-only set involving valgrind elsewhere.
I'm not sure on the cleanest way to modify the build scripts to make this optional. Perhaps allowing /wedge to be somewhere non-root-owned and then installing as a user instead?
The text was updated successfully, but these errors were encountered: