| commit | 25c79197177564be10d4a9441887f998af3579e1 | [log] [tgz] |
|---|---|---|
| author | Daniel Dougherty <doughertyda@fuchsia.infra.roller.google.com> | Thu Jul 14 20:23:40 2022 +0000 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Jul 14 13:25:55 2022 -0700 |
| tree | 52fcd71cb028ee24c2370e5dcbf95f3ed859d179 | |
| parent | fdb26346250372a7c2d27f6a02174813c1bcee6c [diff] |
[roll] Roll fuchsia [ffx] Make config flag relative to CWD Previously, if a relative path was passed to ffx emu for the config template parameter, it would be resolved after the process had changed the working directory, resulting in the inability to use files local to the user's actual CWD. This doesn't make sense in most use cases, as shown by the attached bug. This CL explicitly sets the template files path to be relative to the current working directory of the FFX tool before launching the emulator, so it will always be in line with the user's expectations. Absolute paths are always treated as absolute, so no changes are needed with the handling of those paths. Original-Bug: 95945 Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/699890 Original-Revision: 95a0389dd69b5613b837c9bd000ece317176ce96 GitOrigin-RevId: 46c6f66a0dd470148970ec7f0c31aead3c7307b1 Change-Id: Ic115392fc15552823094efeb4a87f47eb9144af4
This repository contains Fuchsia's Global Integration manifest files.
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.
First install Jiri.
Next run:
$ jiri init $ jiri import minimal https://fuchsia.googlesource.com/integration $ jiri update
Third party projects should have their own subdirectory in ./third_party.