Hi Thomas,
This commit contains a simple change to intel.c patch and three changes to hashes that were needed to build sculpt after this change. Is it normal that each change needs update of hashes of all dependent components? Do I correctly understand that this will force many changes of hashes in repository?
for little tweaks of the boot image like that, I usually side step the depot by building and integrating the affected component directly. This can be achieved by changing the run script as follows:
--- a/repos/gems/run/sculpt.run +++ b/repos/gems/run/sculpt.run @@ -713,6 +713,8 @@ close $fd # Create boot image #
-append boot_modules { } +build { drivers/nic } + +append boot_modules { nic_drv }
build_boot_image $boot_modules
---------
This alleviates the need to rebuild any depot content while testing such changes. See Section 5.5.6. "Accessing depot content from run scripts" - in particular the paragraph "Selectively overriding depot content" - for a description of this feature.
Once the work is complete, a version update of the affected depot content is on order. As pkg/sculpt aggregates src/nic_drv, a new version of src/nic_drv requires a version update of pkg/sculpt.
Cheers Norman