Some projects store multiple Cargo.toml files, let vendor handle all
of them (might be worth having some config for certain Cargo.toml
paths to skip in the future though).
Signed-off-by: William Douglas <william.douglas@intel.com>
Sometimes vendor repos get tagged but the package fails to update for
another reason. In this case the repo wouldn't have the new vendor
ARCHIVE set and new attempts to build would use the old vendor archive
causing failures. Force using the latest vendor tag as generally this
is what we want (if we get a bad vendor tag somehow, it should mean a
new tag needs to be created to replace it anyway).
Signed-off-by: William Douglas <william.douglas@intel.com>
Avoid cases where user git settings cause files to have different line
endings than the package and cause hash mismatches when building.
Signed-off-by: William Douglas <william.douglas@intel.com>
autospec learned how to use 'cargo vendor' output as a drop in
configuration file so put the output of cargo vendor there.
Signed-off-by: William Douglas <william.douglas@intel.com>
Changes vendor from a target (it could still have a stand-alone target
but it wouldn't be used by the autospec target).
This change is needed because the Makefile is rewritten in the
autospec target but the ARCHIVES make variable is going to use the
value when make is executed. The common change causes the ARCHIVES
value to be eval'd during the autospec target execution in order for
the update from the vendor script to be seen by make.
The vendor script changes fix bugs in updating the options.conf and
Makefile. It also now handles returning the original ARCHIVES value as
well as prevent subshell scripts from outputting and adding badness
into the eval'd ARCHIVES variable.
Signed-off-by: William Douglas <william.douglas@intel.com>
This file is used for spec and upstream content so updating it is
important for improving the build automation.
Signed-off-by: William Douglas <william.douglas@intel.com>
Add handling for a vendor target that will handle specific vendor
requirements from a package's options.conf.
The initial change adds handling for 'cargo vendor', creating a new
repo in the configured git repositiory and setting up the ARCHIVES
variable in the package's Makefile.
If the repo already exists, the tooling will check if a repo change
was detected after re-vendoring the sources. If a change is detected
the new content will be pushed and the ARCHIVES variable will be
updated.
Signed-off-by: William Douglas <william.douglas@intel.com>
William Douglas