At the moment I've added 6c77438, which makes a single module workflow much nicer, however if there are multiple modules at play, then it becomes much more annoying.
(github.com/example/cmd/x:mod + golang.org/x/sync):mod
It would be nicer if you could somehow specify the prefix or regular expression on what to include or exclude. For example:
github.com/example/cmd/x:regex(github.com/.*)
github.com/example/cmd/x:+regex(github.com/.*)
github.com/example/cmd/x:-regex(github.com/.*)
// or maybe with quotes, but using nested quotes on command line is rather annoying
github.com/example/cmd/x:regex("github.com/.*")
github.com/example/cmd/x:+regex("github.com/.*")
github.com/example/cmd/x:-regex("github.com/.*")
Similarly:
github.com/example/cmd/x:+mod(golang.org/x/sync)
github.com/example/cmd/x:-mod(golang.org/x/sync)
It would be also possible to use non-selector syntax:
shared(github.com/example/cmd/x:all, mod(golang.org/x/sync) + mod(golang.org/x/tools))
But, this would imply reworking the entire package set graph concept to something that would allow also include "module selectors".
At the moment I've added 6c77438, which makes a single module workflow much nicer, however if there are multiple modules at play, then it becomes much more annoying.
It would be nicer if you could somehow specify the prefix or regular expression on what to include or exclude. For example:
Similarly:
It would be also possible to use non-selector syntax:
But, this would imply reworking the entire package set graph concept to something that would allow also include "module selectors".