Remote platforms

[kerberjg]

💖 Allows you to include platforms from remote repos via --remote=<git url>
Also:

• Specify tag/commit: --remote=<git url>#<ref>
• Specify branch: --remote=<git url>#heads/<branch>

What this does:

• Clones repository into app/
• Links app/<your repo>/configs/*.json into configs/remote_*.json

This allows you to include your own configs, patches, platforms, apps, plugins, packages without modifying anything! 🥳

Also includes cross-config envvar append ✨ : if you want to be able to append to an envvar from another config (such as a remote one), you simply declare it as following:

{
  ...
  "env": {
    "+PLUGIN_ARGS": "-DBUILD_SPECIAL_PLUGIN=ON"
    ...

Specifying a separator is also possible, just put it in parenthesis following the +:

{
  ...
  "env": {
    "+(;)EXT_PLUGINS_DIRS": "$FLUTTER_WORKSPACE/app/my_special_plugins/"
    ...

^ this will make sure that a ; is used when concatenating with the previous value (makes sure it's not used at the beginning/end of a string, only in the middle)

[jwinarske]

@kerberjg As a followup to our discussion. The workspace-automation --config option that exists today is intended to use a different configs folder altogether. Oppose to augmenting, you just cherry pick what you want in your local "configs" path, then pass that path in to the upstream flutter_workspace.py. Flutter_workspace.py can be a symlink in your custom configs folder; which is how I did it for AGL; different targets, etc. Removal of patches/configs should happen in an isolated PR. If the feature is blah, then PR should only cover blah.

[dl9pf]

Excellent. Then we can host our configs in our tree. +1 !

[jwinarske]

@kerberjg I will merge this without the configs/desktop-homescreen.json changes. Can you remove the changes in configs/desktop-homescreen.json? Once it's merged then you can re-base your feature branch; at which point it should just have changes in configs/desktop-homescreen.json. Thanks!

[kerberjg]

@jwinarske sounds good!

[kerberjg]

@jwinarske In order for this to work, I have to either:

A: keep some changes in desktop_homescreen.json
B: remove changes in desktop_homescreen.json and make changes to other files

Which one is more preferrable?

[jwinarske]

@kerberjg as discussed last week, the goal is to prevent any breaking changes to existing CI/test and simply enable the remote append feature for AGL.

[kerberjg]

@jwinarske Should be ready to go

[jwinarske]

cc @dl9pf