cabal gen-bounds ignores project file

[alt-romes]

Describe the bug

Running cabal gen-bounds in a project whose cabal package is not in the root will fail to recognize the package:

To Reproduce
Steps to reproduce the behavior:

cd $(mktemp -d)
cabal init -m -n --exe bad
echo 'packages: bad' > cabal.project
cabal gen-bounds bad

Results in

Error: cabal: No cabal file found.
Please create a package description file <pkgname>.cabal

Expected behavior
Should gen-bounds for the bad package (which is located in the bad directory)

System information

• cabal 3.10, HEAD

[alt-romes]

Same for cabal outdated

[ffaf1]

The documentation does not imply targets for gen-bound, but it does ([PACKAGES]) for outdated.

[ffaf1]

Documentation: --help, Manual is correct.

[alt-romes]

I see. Do you think it would be reasonable to make it work with projects?

This came up because I'm unable to do cabal gen-bounds for a package in a project whose dependencies are local...

[ulysses4ever]

Perhaps duplicate of:

• gen-bounds does not work in multiprojects #7504

[ffaf1]

It would be welcome, the only drawbacks that come to mind are:

• possibly breaking old workflows (shouldn't be the case)
• having to update tests by adding an empty cabal.project.