PSA: 301: mojo/public has moved

[Viet-Trung Luu]

The domokit mojo repo now uses DEPS to pull in mojo/public from https://fuchsia.googlesource.com/mojo/public.

As such, changes should be made to the fuchsia mojo/public repo (reviewed via gerrit), and DEPS will have to be rolled to get the changes to the domokit mojo build.

[Viet-Trung Luu]

Also:

• Fuchsia does not yet consume this new repo, but it will very shortly.
  
• The domokit mojo_sdk repo is now dead, i.e., will no longer be updated. (However, anyone using mojo_sdk repo should be able to simply substitute the fuchsia mojo/public repo.)

[Viet-Trung Luu]

I also just did the same thing for the mojom subdirectory -- it's now DEPSed in from https://fuchsia.googlesource.com/mojom.

On Tue, Aug 16, 2016 at 1:16 PM, Viet-Trung Luu <viettr...@chromium.org> wrote:

[Vardhan Mudunuru]

The manifest [repo] doesn't include the new mojom repo yet (ie `jiri update` doesn't pull it down)

--
You received this message because you are subscribed to the Google Groups "mojo-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mojo-dev+unsubscribe@chromium.org.

[Viet-Trung Luu]

That's true. Patches welcome. :P

(Obviously, it's trivial to add it to the manifest. But we probably also want to set up something in buildtools to download an appropriate Go, etc.)