paperclip4465

Yes, I imagine it is an easy fix, but I’m not competent enough with python to determine what part actually comes up with those paths.

https://github.com/zephyrproject-rtos/zephyr/pull/16368/commits/62d611a3f8645c74f56f375a8e06b0143b4c34e7 It turns out this is not the way it always has been. The desire to move to relative paths was ironically in the name of reproducibility. I am working...

> Symbolic links are "quick hacks", they cause countless other issues In this case it is not a quick hack. The functional deployment model as described in the paper I...

I did read the article and it highlights the problems of treating the filesystem as unstructured memory. I did not want to go so far into the weeds because it...

> "not supported" does NOT imply "reject all small and harmless fixes for specific symlink situations", far from it. Of course I don't expect the project to bend over backwards...

> Absolute paths are really not the way forward: https://reproducible-builds.org/docs/build-path/ I don't think there should be any expectation that builds run from different points in the filesystem should be identical,...

> Of course both people need to be trying to build the same thing but asking them to use the same user name and same /home/johndoe/zephyrproject directory is really too...

> do you realize that Zephyr project and many other dependant projects use [west tool](https://docs.zephyrproject.org/latest/develop/west/index.html) perform most of the operations? Do you realize, that west tool by design works on...