I don't think you want to use go mod or replace directives any more, that's been replaced (for me at any rate) with go work
so, example, suppose I am working in my cpu directory (github.com/u-root/cpu, and I want my cpu command to pull from a locally changed u-root My cpu directory is ~/cpu, and u-root is ~/u-root. I would do this cd ~/cpu go work init go work use ~/u-root and now I'm using a local copy. The nice part about this is it does not change any files that are managed by git. I've been very happy with go work On Thu, May 8, 2025 at 11:32 AM fish4terrisa-MSDSM <[email protected]> wrote: > > ok thx. > Also I saw that nearly all code in x/sys is share with the go toolchain, and > it seems that these packages are generated from the go toolchain source code. > Does anyone know any clues about it? Or I need to manually edit the x/sys > source code? > 9fans / 9fans / see discussions + participants + delivery options Permalink ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/T875b01e7d1d3d05b-M2e36ca9f8c45ebe1d77b3fda Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
