File args only operate on the targets that "own" the source file, as determined by

SourcesField

and

SecondaryOwnerMixin

This means that

./pants list '**/*'

gives different results than

./pants list ::

(even if you didn't consider our weirdness with generated targets not showing up in project introspection goals)

Concrete use case, do we agree that `./pants package cmd/casload`—a Go package with a file-less

go_binary

target in it—should package the

go_binary

? That seems like "obviously, yes!" to me. But want to double check

./pants list 3rdparty/python

would list all

python_requirement

targets defined there (and possibly in subdirs, if recursive)

independent of recursion, i think that

dir:

and

dir::

should match generated targets.