Page MenuHomeFreeBSD

nanobsd: Use NANO_NAME
Needs ReviewPublic

Authored by senguptaangshuman17_gmail.com on Wed, Aug 19, 10:25 AM.
Tags
None
Referenced Files
F168804113: D58972.id184846.diff
Sun, Aug 30, 6:03 AM
F168784181: D58972.id184338.diff
Sun, Aug 30, 3:34 AM
F168755776: D58972.id185115.diff
Sat, Aug 29, 11:58 PM
F168731926: D58972.diff
Sat, Aug 29, 9:01 PM
F168724959: D58972.id184523.diff
Sat, Aug 29, 8:07 PM
F168724354: D58972.id184523.diff
Sat, Aug 29, 8:03 PM
F168695620: D58972.id184523.diff
Sat, Aug 29, 4:32 PM
F168677691: D58972.diff
Sat, Aug 29, 2:13 PM
Subscribers

Details

Reviewers
jlduran
jrm
ashish
Summary

Interpolate NANO_NAME into NANO_IMGNAME instead of hard coding the
full tag into the image name.

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Skipped
Unit
Tests Skipped
Build Status
Buildable 75806
Build 72689: arc lint + arc unit

Event Timeline

tools/tools/nanobsd/defaults.sh
63

This will force several changes in our internal tooling...

tools/tools/nanobsd/defaults.sh
63

This will force several changes in our internal tooling...

Default NANO_NAME is still full, so NANO_IMGNAME still resolves to _.disk.full by default. Only configs that override NANO_NAME to a non-default value would see the image name and NANO_OBJ dir change, and for those the old hardcoded _.disk.full was arguably already wrong (image name not reflecting the actual variant built).