- Avoid chrooting to uninstall pkg, as it will not be installed in the first place.
- Add metalog entries.
Details
Details
- Reviewers
emaste cperciva - Group Reviewers
releng - Commits
- rG8027de008d9f: release: Prepare EC2 cloudware images to be buildable as non-root
Diff Detail
Diff Detail
- Repository
- rG FreeBSD src repository
- Lint
Lint Not Applicable - Unit
Tests Not Applicable
Event Timeline
release/tools/ec2-builder.conf | ||
---|---|---|
59 | Do we have cases where we'd add ./boot/loader.conf twice? (E.g., here and in ec2.conf) |
release/tools/ec2-builder.conf | ||
---|---|---|
59 | Yes. It can happen even more than that, e.g., vmimage.subr will add loader.conf entries if the root file system is on ZFS. It's harmless to have duplicate entries. I suspect the right solution is to have each cloudware variant specify its modifications declaratively rather than having code which hacks up the image in various ad-hoc ways. |