[roll] Roll fuchsia [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.

Original-Bug: b/366083446

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1117776
Original-Revision: 0a519a95f62f1b0876293ce08b6fec197fe33446
GitOrigin-RevId: 1a5b20a5db62954d8bd798393ee717ac777851b7
Change-Id: Ifca253ead0118c03ba850012a8b1865f9c9703df
1 file changed
tree: cc37290e0ce2dd08d6432d93a889febec5d7ad7c
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. cts
  6. firmware
  7. flower
  8. jiri.lock
  9. MILESTONE
  10. minimal
  11. prebuilts
  12. README.md
  13. stem
  14. test_durations
  15. toolchain
README.md

Integration

This repository contains Fuchsia's Global Integration manifest files.

Making changes

All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.

Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance via the IRC channel #fuchsia on Freenode.

Obtaining the source

First install Jiri.

Next run:

$ jiri init
$ jiri import minimal https://fuchsia.googlesource.com/integration
$ jiri update

Third party

Third party projects should have their own subdirectory in ./third_party.