[assembly] Give developer overrides allowlisting a better error message

The definition of developer overrides targets is currently restricted
to local-only locations (they cannot be checked into the tree and used
from there).

This is to surface use-cases and discuss whether they are best
defined as local settings, or features that need to be added to
the platform configuration schema and rules.

This change gives this restriction a better error message than
the 'dependency not allowed' visibility restriction that it
currently has.

Bug: b/366083446

Change-Id: I2957aa5188951864d24f1615231abfa88263367f
Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1117776
Reviewed-by: Aidan Wolter <awolter@google.com>
Commit-Queue: Auto-Submit <auto-submit@fuchsia-infra.iam.gserviceaccount.com>
Fuchsia-Auto-Submit: Aaron Wood <aaronwood@google.com>
2 files changed
tree: ca931e60809780c0fa5c303d3067417442a989d8
  1. boards/
  2. build/
  3. bundles/
  4. docs/
  5. examples/
  6. infra/
  7. products/
  8. scripts/
  9. sdk/
  10. src/
  11. third_party/
  12. tools/
  13. zircon/
  14. .clang-format
  15. .clang-tidy
  16. .editorconfig
  17. .git-blame-ignore-revs
  18. .gitattributes
  19. .gitignore
  20. .gitmodules
  21. .gn
  22. .ignore
  23. analysis_options.yaml
  24. AUTHORS
  25. BUILD.gn
  26. CODE_OF_CONDUCT.md
  27. CONTRIBUTING.md
  28. fuchsia.code-workspace
  29. LICENSE
  30. OWNERS
  31. PATENTS
  32. pyproject.toml
  33. pyrightconfig.json
  34. README.md
  35. rustfmt.toml
  36. shac.star
  37. shac.textproto
README.md

Fuchsia

What is Fuchsia?

Fuchsia is an open source, general purpose operating system supporting modern 64-bit Intel and ARM processors.

We expect everyone interacting with our project to respect our code of conduct.

Read more about Fuchsia's principles.

How can I build and run Fuchsia?

See Getting Started.

Where can I learn more about Fuchsia?

See fuchsia.dev.