A couple of comments:
One thing I'm missing is the ability to do mono-repo imports. Say we
want to vendor in
https://github.com/projectfluent/fluent.js/tree/master/fluent-gecko.
For js libraries, we might also want to pay attention to .npmignore
(others already mentioned hg, so also .hgignore).
There's no spec what happens with patches that fail to apply, or failed
run_after scripts.
Do we intend to do something if the LICENSE changes? Also, what are we
supposed to do if the vendored code doesn't have a LICENSE file?
Axel
Am 10.04.18 um 06:25 schrieb glob:
mozilla-central contains code vendored from external sources. Currently
there is no standard way to document and update this code. In order to
facilitate automation around auditing, vendoring, and linting we intend
to require all vendored code to be annotated with an in-tree YAML file,
and for the vendoring process to be standardised and automated.
The plan is to create a YAML file for each library containing metadata
such as the homepage url, vendored version, bugzilla component, etc. See
https://goo.gl/QZyz4xfor the full specification.
We will work with teams to add moz.yaml files where required, as well as
adding the capability for push-button vendoring of new revisions.
Please address comments to the dev-platform list.
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
