Hugues Morisset

As a workaround for this issue, I've been doing something similar to this : ``` buildfile = text_file( name="BUILD.plz", visibility=["PUBLIC"], strip=True, content=f""" CONFIG["OS"] = '{goos}' CONFIG["ARCH"] = '{goarch}' CONFIG["GO"] =...

This is actually the thinking behind the stacktrace pull request https://github.com/thought-machine/please/pull/2896 to have more information in the parse scope.

#2896 was closed as stall :/

One solution would be to use bash array and associative arrays, maybe please could generate a 'pre-script' containing ``` declare -a TOOLS=("/dir/with spaces/proj" "/dir2") # For named args declare -A...

It seems to me, that subrepos should check if the rule declared as `dep` `needsBuilding`

Retaking the example repo `https://github.com/Wuageorg/please_issue_2943` the dependency graph is ``` $ please query deps //dir1 //dir1:dir1 //dir1:subrepo ///dir1/this_subrepo//:build ``` Subrepos could implies dependencies on their declared `dep`. In this case...

Maybe the operation is not clear, I get this bug when modifying the source file `dir1/script.sh` and **not** the one inside the subrepo. It does trigger a rebuild for `//dir1:subr_srcs`...

While I understand the intention behind keeping the build language minimal, having stacktrace feature can improve debugging and development efficiency. It can also be beneficial for newcomers as a way...

I still would like this feature, to auto generate rules name from the function name or the N-1 function name. Is there an alternative way to do this ?

Works great for me, thanks!